You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Toivo Adams (JIRA)" <ji...@apache.org> on 2015/12/05 12:39:10 UTC

[jira] [Commented] (NIFI-1251) Allow ExecuteSQL to send out large result sets in chunks

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

Toivo Adams commented on NIFI-1251:
-----------------------------------

Should be back pressure also supported during query execution?
I mean after creating say 100 Flowfiles, creating new FlowFiles will be suspended and creating new FlowFiles will be resumed during next onTrigger() method call.

Thanks
Toivo


> Allow ExecuteSQL to send out large result sets in chunks
> --------------------------------------------------------
>
>                 Key: NIFI-1251
>                 URL: https://issues.apache.org/jira/browse/NIFI-1251
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Mark Payne
>
> Currently, when using ExecuteSQL, if a result set is very large, it can take quite a long time to pull back all of the results. It would be nice to have the ability to specify the maximum number of records to put into a FlowFile, so that if we pull back say 1 million records we can configure it to create 1000 FlowFiles, each with 1000 records. This way, we can begin processing the first 1,000 records while the next 1000 are being pulled from the remote database.
> This suggestion comes from Vinay via the dev@ mailing list:
> Is there way to have streaming feature when large result set is fetched from
> database basically to reads data from the database in chunks of records
> instead of loading the full result set into memory.
> As part of ExecuteSQL can a property be specified called "FetchSize" which
> Indicates how many rows should be fetched from the resultSet.
> Since jam bit new in using NIFI , can any guide me on above.
> Thanks in advance



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)