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

Posted to issues@nifi.apache.org by "Matt Burgess (JIRA)" <ji...@apache.org> on 2019/04/25 19:47:00 UTC

[jira] [Updated] (NIFI-6244) Allow GenerateTableFetch to partition without a max-value column

     [ https://issues.apache.org/jira/browse/NIFI-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess updated NIFI-6244:
-------------------------------
    Status: Patch Available  (was: In Progress)

> 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
>            Assignee: Matt Burgess
>            Priority: Major
>          Time Spent: 10m
>  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)