[NIFI-2323] Improve handling of Oracle datetime columns in QueryDatabaseTable and GenerateTableFetch

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.6.0
• Fix Version/s: 1.2.0
• Assignee: Matt Burgess
• Reporter: Matt Burgess
• Created: 19/Jul/16 20:37
• Updated: 06/Apr/18 18:51
• Resolved: 25/Apr/17 14:00

Description

Due to default handling of Oracle columns returned as java.sql.Date types, the string literals used to compare against the column values must be in the same format as the NLS_DATE_FORMAT setting of the database (often YYYY-MM-DD).

I believe when "Oracle" is provided as the database type (formerly known as pre-processing strategy), Oracle's Datetime Functions (such as TO_DATE or TO_TIMESTAMP) could be leveraged to give more fine-grained maximum-value information.

Issue Links

• is cloned by: NIFI-5049 Fix handling of Phonenix datetime columns in QueryDatabaseTable and GenerateTableFetch
• links to: GitHub Pull Request #1664