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

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

Github user mattyb149 commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/3051#discussion_r237152109
  
    --- Diff: 
nifi-nar-bundles/nifi-cassandra-bundle/nifi-cassandra-processors/src/main/java/org/apache/nifi/processors/cassandra/QueryCassandra.java
 ---
    @@ -269,11 +313,17 @@ public void process(final OutputStream out) throws 
IOException {
                 // cap the error limit at 10, format the messages, and don't 
include the stack trace (it is displayed by the
                 // logger message above).
                 getLogger().error(nhae.getCustomMessage(10, true, false));
    +            if (fileToProcess == null) {
    +                fileToProcess = session.create();
    +            }
                 fileToProcess = session.penalize(fileToProcess);
                 session.transfer(fileToProcess, REL_RETRY);
    -
             } catch (final QueryExecutionException qee) {
    +            //session.rollback();
    --- End diff --
    
    There are a few spots of commented out code, please remove if not 
necessary, thanks!


> QueryCassandra processor : output FlowFiles as soon fetch_size is reached
> -------------------------------------------------------------------------
>
>                 Key: NIFI-5642
>                 URL: https://issues.apache.org/jira/browse/NIFI-5642
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.7.1
>            Reporter: André Gomes Lamas Otero
>            Priority: Major
>
> When I'm using QueryCassandra alongside with fetch_size parameter I expected 
> that as soon my reader reaches the fetch_size the processor outputs some data 
> to be processed by the next processor, but QueryCassandra reads all the data, 
> then output the flow files.
> I'll start to work on a patch for this situation, I'll appreciate any 
> suggestion.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to