[
https://issues.apache.org/jira/browse/NIFI-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709144#comment-17709144
]
ASF subversion and git services commented on NIFI-5642:
-------------------------------------------------------
Commit 4f22f0985a58f6e8a36edea9f6c907f758945357 in nifi's branch
refs/heads/support/nifi-1.x from aglotero
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4f22f0985a ]
NIFI-5642: QueryCassandra processor : output FlowFiles as soon fetch_size is
reached
NIFI-5642: QueryCassandra processor : output FlowFiles as soon fetch_size is
reached
Fixed checkstyle error
Delete build.sh
Delete local build file
NIFI-5642 : letting fetch_size to control the Cassandra data flow creating a
new MAX_ROWS_PER_FLOW_FILE parameter
Fixed checkstyle error: no more import java.util.*
Fixed missing imports
NIFI-5642: added REL_ORIGINAL relationship in order to allow incremental commit
Addressing comments from code review
Adjustments on timestamp datatype formatting
Created the OUTPUT_BATCH_SIZE property
Code review adjustments
NIFI-5642: update after rebase
NIFI-5642: addressing PR comments
NIFI-5642: adding in integration test, fixing race condition
NIFI-5642: remove log4j2
This closes #6848
Signed-off-by: Mike Thomsen <mthom...@apache.org>
> 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
> Assignee: Levi Lentz
> Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)
