[ https://issues.apache.org/jira/browse/NIFI-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826401#comment-16826401 ]
Matt Burgess commented on NIFI-6244: ------------------------------------ I tested Derby, Postgres, Oracle 11 & 12, MySQL, MSSQL 2017, and I believe the problem only exists for MSSQL 2008 and 2012+. I propose to add newid() as the default order by clause if one is not provided to the adapter (i.e. no max-value column was set for the processor). This would apply only to the MSSQL adapters. > 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: Improvement > Reporter: Matt Burgess > Priority: Major > > 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)