[
https://issues.apache.org/jira/browse/NIFI-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated NIFI-7824:
-------------------------------
Status: Patch Available (was: Open)
> GenerateTableFetch Improvement
> ------------------------------
>
> Key: NIFI-7824
> URL: https://issues.apache.org/jira/browse/NIFI-7824
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: ZhangCheng
> Assignee: ZhangCheng
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ‘Custom ORDER BY Column’ should have a higher priority than 'Maximum-value
> Columns' for genarating query sqls when using 'order by'.
> For example: we usually use timestamp column as the 'Maximum-value Columns' ,
> and Many values of timestamp are often the same. In this case, querying data
> often results in duplicate data because of 'order by timestamp '.So if we use
> timestamp as 'Maximum-value Columns' ,and use a unique column as ‘Custom
> ORDER BY Column’, and use 'order by unique column ', we would not query
> duplicate data.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
