[
https://issues.apache.org/jira/browse/NIFI-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15514913#comment-15514913
]
ASF GitHub Bot commented on NIFI-2803:
--------------------------------------
GitHub user combineads opened a pull request:
https://github.com/apache/nifi/pull/1052
NIFI-2803 The pagination of GenerateTableFetch has a sort bug
When data is coming to the ingested table, the pagination SQL needs the
ORDER BY statement with maxValueClauses.
If maxValueClauses are not the primary keys, incoming data usually inserts
using primary keys. So when ExecuteSQL executes, some data may be lost.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/combineads/nifi NIFI-2803
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1052.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1052
----
commit d27e5380ed490ee1aecd27a487b32b36e80c2594
Author: Byunghwa Yun <[email protected]>
Date: 2016-09-23T00:21:21Z
NIFI-2803 The pagination of GenerateTableFetch has a sort bug.
----
> The pagination of GenerateTableFetch has a sort bug.
> ----------------------------------------------------
>
> Key: NIFI-2803
> URL: https://issues.apache.org/jira/browse/NIFI-2803
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.0.0
> Reporter: Byunghwa Yun
>
> When data is coming to the ingested table, the pagination SQL needs the ORDER
> BY statement with maxValueClauses.
> If maxValueClauses are not the primary keys, incoming data usually inserts
> using primary keys. So when ExecuteSQL executes, some data may be lost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
