[jira] [Updated] (NIFI-4903) Database Fetch processors cannot handle timestamp fields with Oracle 12+

2018-02-22 Thread Pierre Villard (JIRA) 

 [ 
https://issues.apache.org/jira/browse/NIFI-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Villard updated NIFI-4903:
-
   Resolution: Fixed
Fix Version/s: 1.6.0
   Status: Resolved  (was: Patch Available)

> Database Fetch processors cannot handle timestamp fields with Oracle 12+
> 
>
> Key: NIFI-4903
> URL: https://issues.apache.org/jira/browse/NIFI-4903
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
> Fix For: 1.6.0
>
>
> When using GenerateTableFetch or QueryDatabaseTable with an Oracle 12+ 
> adapter, if the maximum value column is set to a column of type timestamp, 
> then upon the second fetch the following error occurs:
> java.sql.SQLDataException: ORA-01843: not a valid month
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (NIFI-4903) Database Fetch processors cannot handle timestamp fields with Oracle 12+

2018-02-22 Thread Matt Burgess (JIRA) 

 [ 
https://issues.apache.org/jira/browse/NIFI-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess updated NIFI-4903:
---
Status: Patch Available  (was: In Progress)

> Database Fetch processors cannot handle timestamp fields with Oracle 12+
> 
>
> Key: NIFI-4903
> URL: https://issues.apache.org/jira/browse/NIFI-4903
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
>
> When using GenerateTableFetch or QueryDatabaseTable with an Oracle 12+ 
> adapter, if the maximum value column is set to a column of type timestamp, 
> then upon the second fetch the following error occurs:
> java.sql.SQLDataException: ORA-01843: not a valid month
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)