[ https://issues.apache.org/jira/browse/NIFI-12526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess reassigned NIFI-12526: ----------------------------------- Assignee: Matt Burgess > QueryCassandra should not output FlowFiles as soon as the "available rows > without fetching" is reached > ------------------------------------------------------------------------------------------------------ > > Key: NIFI-12526 > URL: https://issues.apache.org/jira/browse/NIFI-12526 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Reporter: Matt Burgess > Assignee: Matt Burgess > Priority: Major > Fix For: 1.25.0, 2.0.0 > > > NIFI-5642 introduced the Max Rows Per Flow File and Output Batch Size > properties to QueryCassandra, but still uses the internal > "rowsAvailableWithoutFetching" variable (whose value comes from the Cassandra > ResultSet and defaults to 5000) as a trigger to stop processing rows for a > FlowFile. This can cause unexpected behavior, such as getting multiple > FlowFiles when only one is expected. > NIFI-5642 also removes the Compression Type property, which might be ok for > 2.x but will cause all flows using this property in 1.x to become invalid. On > the support (1.x) branch we need to add the property back in, perhaps we can > keep it removed for 2.x but we'd want to remove the Cassandra Connect Points > property and such to force the user to use a Cassandra Connection controller > service. The reason to add the property back is if the Cassandra Contact > Points property is used instead of the Cassandra Connection controller > service, there is no way to set the Compression Type. -- This message was sent by Atlassian Jira (v8.20.10#820010)