Is there a way to have dsbulk reuse the connection object instead of doing the connection for each table for the same keyspace.
Is there a way to have dsbulk reuse the connection object instead of doing the connection for each table for the same keyspace.
@maruti.nitj_91373 The DSBulk utility isn't designed to be a long-running application and is meant to be run on one table at a time.
What is your concern about DSBulk opening new connections to the cluster when you load/unload a table? If you give us additional information on what you're trying to achieve, we might be able to provide a solution. Cheers!
When we use dsbulk to unload and load data from multiple tables , assume its a script invoked with a while loop for each table in the key space, idea is just to have a way for dsbulk to establish the connection once and load different tables in the key space. But I See the utility is designed to run one table @ a time , so I believe that answers my question.
5 People are following this question.
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