[
https://issues.apache.org/jira/browse/NIFI-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856741#comment-16856741
]
ASF subversion and git services commented on NIFI-6348:
-------------------------------------------------------
Commit 1d18735076d134af2ec7c484c982746e261ed4a5 in nifi's branch
refs/heads/master from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1d18735 ]
NIFI-6348: Added Custom ORDER BY Column property to GenerateTableFetch
NIFI-6348: Fixed doc
This closes #3515.
Signed-off-by: Bryan Bende <[email protected]>
> Allow GenerateTableFetch to order on a column without a Max-Value column
> ------------------------------------------------------------------------
>
> Key: NIFI-6348
> URL: https://issues.apache.org/jira/browse/NIFI-6348
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Related to NIFI-6244, if no Max-Value Column is set for GenerateTableFetch,
> and Partition Size > 0 (meaning paging/partitioning is done), then no column
> has been specified for ordering the rows. When fetching multiple pages, this
> causes the ordering of each fetch to be arbitrary (i.e. different ordering
> for each fetch), which can result in missing and/or duplicate rows. In the
> case of SQL Server, the parser will actually throw an error when no ORDER BY
> clause is provided. NIFI-6244 aimed to fix that but it was not a correct
> solution so was reverted.
> This Jira proposes to add a "Custom ORDER BY Column" property, which will be
> used only if Max-Value Column is not set and Partition Size > 0. It is not
> required, but the documentation should explain that not using this field can
> result in the behavior above.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
