Are Batch transactions ( Insert update delete) prefered way of doing bulk operation s in cassandra or do we need to rely on ssbload , DSE Bulk Loader , Capture and Copy ?
Thanks
No, definitely not. :) BATCH
statements are designed to achieve atomicity when updating multiple tables. Atomic updates are when you need ALL inserts/updates to be applied otherwise NONE should apply.
Unlike relational databases, BATCH
statements are not an optimisation -- it can decrease throughput and increase latency if not used properly since it can overload the coordinator nodes making them unresponsive.
I recommend the following documents for more info:
Cheers!
6 People are following this question.
How does data stay consistent if a batch fails midway through?
Getting error "Logged batches are not supported for this type of batch requests"
TOKEN() query returning "no viable alternative at input 'TOKEN()'"
Cannot start Cassandra due to "Unexpected disk state: failed to read transaction log"
Cassandra LOCAL_QUORUM is waiting for remote datacenter responses
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2023 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use