[
https://issues.apache.org/jira/browse/NIFI-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982912#comment-15982912
]
ASF subversion and git services commented on NIFI-2323:
-------------------------------------------------------
Commit 9ed001869b4887f57e108764354557391092ecab in nifi's branch
refs/heads/master from [~mattyb149]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=9ed0018 ]
NIFI-2323: Fixed Oracle timestamp handling in DB fetch processors. This closes
#1664.
> 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
> Fix For: 1.2.0
>
>
> 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)
