[jira] [Commented] (FLINK-36303) PostgreSQL timestamp precision 0 not supported

2024-09-17 Thread Ken Geis (Jira)
[ https://issues.apache.org/jira/browse/FLINK-36303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882542#comment-17882542 ] Ken Geis commented on FLINK-36303: -- I've created a pull request that fixes this. [flink

[jira] [Updated] (FLINK-36303) PostgreSQL timestamp precision 0 not supported

2024-09-17 Thread Ken Geis (Jira)
[ https://issues.apache.org/jira/browse/FLINK-36303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Geis updated FLINK-36303: - Description: I am having trouble with Flink 3.2.0 recognizing my timestamp(0) columns in PostgreSQL 15.

[jira] [Created] (FLINK-36303) PostgreSQL timestamp precision 0 not supported

2024-09-17 Thread Ken Geis (Jira)
Ken Geis created FLINK-36303: Summary: PostgreSQL timestamp precision 0 not supported Key: FLINK-36303 URL: https://issues.apache.org/jira/browse/FLINK-36303 Project: Flink Issue Type: Bug

[jira] [Commented] (FLINK-9395) Outer Joins with array types on the outer join input fail

2019-09-30 Thread Ken Geis (Jira)
[ https://issues.apache.org/jira/browse/FLINK-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941521#comment-16941521 ] Ken Geis commented on FLINK-9395: - Good news. This worked for me using the Blink planner.

[jira] [Commented] (FLINK-9395) multiple left outer joins to subqueries with array values fail

2018-05-17 Thread Ken Geis (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479422#comment-16479422 ] Ken Geis commented on FLINK-9395: - It appears that the faulty logic is in {{DataSetJoin.pa

[jira] [Created] (FLINK-9395) multiple left outer joins to subqueries with array values fail

2018-05-17 Thread Ken Geis (JIRA)
Ken Geis created FLINK-9395: --- Summary: multiple left outer joins to subqueries with array values fail Key: FLINK-9395 URL: https://issues.apache.org/jira/browse/FLINK-9395 Project: Flink Issue Typ

[jira] [Closed] (FLINK-9341) Oracle: "Type is not supported: Date"

2018-05-15 Thread Ken Geis (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-9341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Geis closed FLINK-9341. --- Resolution: Not A Bug This issue happened because because I used BasicTypeInfo.DATE_TYPE_INFO in my input for

[jira] [Commented] (FLINK-9341) Oracle: "Type is not supported: Date"

2018-05-14 Thread Ken Geis (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-9341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475297#comment-16475297 ] Ken Geis commented on FLINK-9341: - Thanks, [~fhueske]. I meant to do this initially. I've

[jira] [Updated] (FLINK-9341) Oracle: "Type is not supported: Date"

2018-05-11 Thread Ken Geis (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-9341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Geis updated FLINK-9341: Description: When creating a Table from an Oracle JDBCInputFormat with a date column, I get the errorĀ "Type

[jira] [Created] (FLINK-9341) Oracle: "Type is not supported: Date"

2018-05-11 Thread Ken Geis (JIRA)
Ken Geis created FLINK-9341: --- Summary: Oracle: "Type is not supported: Date" Key: FLINK-9341 URL: https://issues.apache.org/jira/browse/FLINK-9341 Project: Flink Issue Type: Bug Component

[jira] [Commented] (FLINK-7221) JDBCOutputFormat swallows errors on last batch

2017-07-25 Thread Ken Geis (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-7221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100855#comment-16100855 ] Ken Geis commented on FLINK-7221: - Unfortunately, my employer (UC Berkeley) is reluctant t

[jira] [Commented] (FLINK-7221) JDBCOutputFormat swallows errors on last batch

2017-07-20 Thread Ken Geis (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-7221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094924#comment-16094924 ] Ken Geis commented on FLINK-7221: - [~fhueske], I'd be glad to submit a patch. I'm currentl

[jira] [Created] (FLINK-7221) JDBCOutputFormat swallows errors on last batch

2017-07-18 Thread Ken Geis (JIRA)
Ken Geis created FLINK-7221: --- Summary: JDBCOutputFormat swallows errors on last batch Key: FLINK-7221 URL: https://issues.apache.org/jira/browse/FLINK-7221 Project: Flink Issue Type: Bug

[jira] [Commented] (FLINK-3445) make JDBCInputFormat implement ResultTypeQueryable

2016-02-24 Thread Ken Geis (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163206#comment-15163206 ] Ken Geis commented on FLINK-3445: - Unfortunately for this, I've fallen back on working wit

[jira] [Commented] (FLINK-3471) JDBCInputFormat cannot handle null fields of certain types

2016-02-23 Thread Ken Geis (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159028#comment-15159028 ] Ken Geis commented on FLINK-3471: - There is current code in JDBCInputFormat that avoids Ja

[jira] [Created] (FLINK-3472) JDBCInputFormat.nextRecord(..) has misleading message on NPE

2016-02-22 Thread Ken Geis (JIRA)
Ken Geis created FLINK-3472: --- Summary: JDBCInputFormat.nextRecord(..) has misleading message on NPE Key: FLINK-3472 URL: https://issues.apache.org/jira/browse/FLINK-3472 Project: Flink Issue Type:

[jira] [Created] (FLINK-3471) JDBCInputFormat cannot handle null fields of certain types

2016-02-22 Thread Ken Geis (JIRA)
Ken Geis created FLINK-3471: --- Summary: JDBCInputFormat cannot handle null fields of certain types Key: FLINK-3471 URL: https://issues.apache.org/jira/browse/FLINK-3471 Project: Flink Issue Type: Bu

[jira] [Commented] (FLINK-3445) make JDBCInputFormat implement ResultTypeQueryable

2016-02-19 Thread Ken Geis (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154945#comment-15154945 ] Ken Geis commented on FLINK-3445: - To provide a little more context, I am coding in Groovy

[jira] [Commented] (FLINK-3445) make JDBCInputFormat implement ResultTypeQueryable

2016-02-19 Thread Ken Geis (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154335#comment-15154335 ] Ken Geis commented on FLINK-3445: - One can get ResultSetMetaData by preparing a statement

[jira] [Commented] (FLINK-3445) make JDBCInputFormat implement ResultTypeQueryable

2016-02-18 Thread Ken Geis (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15153589#comment-15153589 ] Ken Geis commented on FLINK-3445: - Thanks! I'm thinking that JDBC ResultSetMetaData could

[jira] [Created] (FLINK-3445) make JDBCInputFormat implement ResultTypeQueryable

2016-02-18 Thread Ken Geis (JIRA)
Ken Geis created FLINK-3445: --- Summary: make JDBCInputFormat implement ResultTypeQueryable Key: FLINK-3445 URL: https://issues.apache.org/jira/browse/FLINK-3445 Project: Flink Issue Type: Improvemen