You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (JIRA)" <ji...@apache.org> on 2017/04/11 16:11:41 UTC

[jira] [Updated] (NIFI-2323) Improve handling of Oracle datetime columns in QueryDatabaseTable and GenerateTableFetch

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

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

> Improve handling of Oracle datetime columns in QueryDatabaseTable and GenerateTableFetch
> ----------------------------------------------------------------------------------------
>
>                 Key: NIFI-2323
>                 URL: https://issues.apache.org/jira/browse/NIFI-2323
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 0.6.0
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)