[
https://issues.apache.org/jira/browse/NIFI-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855673#comment-16855673
]
ASF subversion and git services commented on NIFI-6244:
-------------------------------------------------------
Commit 08d2e698788e47fb11435ab2bcd863563ca72eb7 in nifi's branch
refs/heads/master from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=08d2e69 ]
Revert "NIFI-6244: Provide default ORDER BY clause in MSSQL adapters"
This reverts commit 7fc49c2cb80ce765afd940d1e4209a8677e5d3f2.
This closes #3512
> Allow GenerateTableFetch to partition without a max-value column
> ----------------------------------------------------------------
>
> Key: NIFI-6244
> URL: https://issues.apache.org/jira/browse/NIFI-6244
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> For some RDBMS systems / SQL dialects, it is not valid to try and
> paginate/partition rows without an ORDER BY clause. MS SQL Server 2012+ is
> one example (see
> [here|https://stackoverflow.com/questions/49262675/issue-with-generate-table-fetch-sql-server-2016]
> for more details). However some systems/dialects allow for a "dummy" or
> default ordering, which can be generated when no ordering clause is provided
> to the database adapter. Again with MS SQL Server 2012+ as an example, you
> can ORDER BY newid().
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
