[ 
https://issues.apache.org/jira/browse/NIFI-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946255#comment-15946255
 ] 

ASF GitHub Bot commented on NIFI-3268:
--------------------------------------

Github user ijokarumawak commented on the issue:

    https://github.com/apache/nifi/pull/1376
  
    Hi @qfdk , excuse me for not providing further review comments. Today, I 
wanted to test this updated PR but unfortunately it is conflicted. Would you 
rebase it with the latest master, address merge conflict and squash commits 
into one? Please let us know when it gets ready to resume review.
    
    It may not be ideal, but I think it will take time to get this PR fully 
reviewed with various DBMS to see if it works as expected and how it can 
improve performance. On the other hand, the NiFi community is [discussing about 
releasing 
1.2.0](http://apache-nifi-developer-list.39713.n7.nabble.com/Closing-in-on-a-NiFi-1-2-0-release-td14907.html).
 To make this effort along with the release cycles, can we remove 1.2.0 as Fix 
Version from JIRA [NIFI-3268](https://issues.apache.org/jira/browse/NIFI-3268)? 
The Fix Version is used to track which version the issue is fixed, and should 
be empty until it's resolved.
    
    Thanks for your contribution.


> Add AUTO_INCREMENT column in GenerateTableFetch to benefit index
> ----------------------------------------------------------------
>
>                 Key: NIFI-3268
>                 URL: https://issues.apache.org/jira/browse/NIFI-3268
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.1.1
>         Environment: - ubuntu 16.04
> - java version "1.8.0_111"
> - Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
> - Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)
>            Reporter: qfdk
>              Labels: easyfix
>             Fix For: 1.2.0
>
>
> I added AUTO_INCREMENT column in  GenerateTableFetch to benefit index column
> By default this processor uses OFFSET, i have  problems with large data. 
> somme column has index so we could use index to speed up query time.
> I posted question here :
> https://community.hortonworks.com/questions/72586/how-can-i-use-an-array-with-putelasticsearch.html
> If you indexed un column (id), you could use this sql
> ```
> select xxx
> From xxxxx
> where 200000=>id
> order by id
> limit 200000
> ```
> “OFFSET is bad for skipping previous rows.” [Online]. Available: 
> http://Use-The-Index-Luke.com/sql/partial-results/fetch-next-page. [Accessed: 
> 27-Dec-2016].
> Thank you in advance



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to