[
https://issues.apache.org/jira/browse/NIFI-8383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-8383.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> PutCassandraRecord always uses batch statements
> -----------------------------------------------
>
> Key: NIFI-8383
> URL: https://issues.apache.org/jira/browse/NIFI-8383
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.13.2
> Reporter: Wouter de Vries
> Priority: Major
>
> The PutCassandraRecord processor uses a BatchStatement for all inserts. This
> is not recommended for most situations, particularly when the records that
> are inserted belong to different partitions.
> Instead, we should use parallel/asynchronous insertions to optimize for write
> speed, and still allow batch statements when some form of atomicity is
> required.
> ([https://docs.datastax.com/en/dse/6.0/cql/cql/cql_reference/cql_commands/cqlBatch.html)]
> This setup leads to log warnings of the following form:
> {noformat}
> stdout F WARN [Native-Transport-Requests-3] 2021-03-30 08:33:01,760
> NoSpamLogger.java:94 - Unlogged batch covering 100 partitions detected
> against table [KEYSPACE.TABLE]. You should use a logged batch for atomicity,
> or asynchronous writes for performance.{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
