You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Aurélien DEHAY (JIRA)" <ji...@apache.org> on 2018/05/02 13:56:00 UTC

[jira] [Created] (NIFI-5140) QueryDatabaseTable & GenerateTableFetch date with Oracle

Aurélien DEHAY created NIFI-5140:
------------------------------------

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


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
(v7.6.3#76005)