[
https://issues.apache.org/jira/browse/NIFI-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-5140.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> QueryDatabaseTable & GenerateTableFetch date with Oracle
> ---------------------------------------------------------
>
> Key: NIFI-5140
> URL: https://issues.apache.org/jira/browse/NIFI-5140
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.6.0
> Environment: Oracle 11g
> Reporter: Aurélien DEHAY
> Priority: Major
>
> Hello.
> The QueryDatabaseTable & GenerateTableFetch processors does not work with
> Oracle when the max column is in DATE type, but contains a TIMESTAMP.
> the request is generated with timestamp cast, so Oracle converts every DATE
> to a TIMESTAMP, so it's not using the index. The query is then really slow,
> and falls in timeout.
> The column getColumnTypeName returns DATE, but getColumnClassName returns
> java.sql.Timestamp.
> When I launch the query by hand with a to_date conversion, it's using the
> index.
> NIFI-2323 seems to have introduced this behaviour.
>
> Thanks.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
