[
https://issues.apache.org/jira/browse/NIFI-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702076#comment-16702076
]
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_r237138338
--- Diff:
nifi-nar-bundles/nifi-cassandra-bundle/nifi-cassandra-processors/src/main/java/org/apache/nifi/processors/cassandra/AbstractCassandraProcessor.java
---
@@ -132,17 +134,25 @@
.addValidator(StandardValidators.CHARACTER_SET_VALIDATOR)
.build();
+ // Relationships
public static final Relationship REL_SUCCESS = new
Relationship.Builder()
.name("success")
.description("A FlowFile is transferred to this relationship
if the operation completed successfully.")
.build();
+
+ static final Relationship REL_ORIGINAL = new Relationship.Builder()
+ .name("original")
+ .description("All input FlowFiles that are part of a
successful query execution go here.")
+ .build();
+
public static final Relationship REL_FAILURE = new
Relationship.Builder()
.name("failure")
- .description("A FlowFile is transferred to this relationship
if the operation failed.")
+ .description("CQL query execution failed.")
--- End diff --
I'd prefer `CQL operation` rather than `query`, as PutCassandra is more of
a statement than a query, and this base processor could be used to do other
things. Technically a processor wouldn't have to use CQL although I'm not sure
of other ways to interact with Cassandra, and I think the user would be
comfortable with the term CQL to mean Cassandra, even if it didn't use CQL.
> 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)
