Matt Burgess commented on NIFI-4903:

This is a logic error in AbstractDatabaseFetchProcessor which checks to see if 
the database adapter name is equal to "Oracle". Instead it should check to see 
if the database adapter name contains the string "Oracle", which will allow it 
to work for the Oracle 12+ adapter (whose name is "Oracle 12+") and any future 
Oracle-related adapters. Note I'm calling for "contains" rather than 
"startsWith" to give more flexibility for adapter names (such as "My Special 
Oracle Adapter", e.g.).

> 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
>            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

Reply via email to