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

Posted to issues@nifi.apache.org by "ZhangCheng (Jira)" <ji...@apache.org> on 2019/12/14 08:47:00 UTC

[jira] [Created] (NIFI-6950) GenerateTableFetch Improvement

ZhangCheng created NIFI-6950:
--------------------------------

             Summary: GenerateTableFetch Improvement 
                 Key: NIFI-6950
                 URL: https://issues.apache.org/jira/browse/NIFI-6950
             Project: Apache NiFi
          Issue Type: Improvement
          Components: Extensions
    Affects Versions: 1.9.2
            Reporter: ZhangCheng


See Also https://issues.apache.org/jira/browse/NIFI-5840

When the Max-Value column has many of the same values,there may be duplicate data when paging database.

When I'm in this situation, I usually use the ReplaceText Processor to add the tahle's pk behind 'order by Max-Value-Column '

Maybe we can add the primary key behind the 'order by' if the pk exists in DatabaseAdapter's getSelectStatement() automatically.

Or just like  https://issues.apache.org/jira/browse/NIFI-6348,we allow GenerateTableFetch to order on a column behind the Max-Value column.We could add a 'PK ORDER BY Column',which will be used only if Max-Value Column is set .And we can add the PK manually.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)