java-driver | DataStax Java Driver for Apache Cassandra | Database library

The error occurred because of not exporting the jar with all dependencies. I solved it by using shadowJar to pack all dependencies togather.

Add the following code to build.gradle

You have configured the wrong option on the driver. METADATA_SCHEMA_REQUEST_TIMEOUT is the timeout for the requests to retrieve the schema.

The default request timeout for the Java driver is basic.request.timeout (see reference configuration):

My first approach would be going to:

C:\Users\X.m2\repository\com\google\code\findbugs\jsr305\3.0.2

and delete:

jsr305-3.0.2.jar

and then run a maven clean install or your goal

Sometimes the jars are downloaded corrupted

Andrew is on the right track with his comment. The problem is that the secure connect bundle contains connection metadata plus SSL (TLS) credentials so the driver already expects that encryption is enabled which is the reason the resolver throws this exception:

Is it possible to use mongodb with Apache Camel asynchronously?

Indeed, this is what Apache Camel will be doing under the cover, otherwise, you will find yourself with an application blocking without proceeding with any valuable processing.

Since you have referred to the Channel Adapter (EIP) in your post, I would assume you are trying to implement a MongoDB consumer.

To consume data from a MongoDB database, Apache Camel offers two consumer strategies:

• Tailable Consumer: This strategy is about having a Thead continuously calling for next result on a MongoCursor. This strategy is feasible thanks to MongoDb Tailable Cursor feature which simply allows to have a query cursor open even after exhausting (iterating) results which removes the need to continuously have the former Thread executing the fetch query again and again
• Change Stream Consumer: This strategy on the other hand relies on the MongoDB Changes watch feature with which a client can receive (after subscription) changes for a particular collection. Same as for the Tailable consumer, there will be a Thread running endlessly (unless stopped) listening to changes on the MongoCollection of interest

As you can see, in both strategies, there is no need to perform direct queries for changes processing, unless for initial bootstrapping and resumption, neither using the synchronous Java Driver nor the Reactive Streams Driver.

This error message...

There isn't any magic that happens here since Cassandra is simply using the Java IO utilities so this is a low-level filesystem issue.

One of the things to check for is whether the existing commit logs in the directory are owned by a different user that the Cassandra process does not have access to. For example, CommitLog-6-1642719269564.log is owned by root but the C* process is running with cassandra. If so, you will need to change the file ownership. Cheers!

[UPDATE] Java 11 is only supported from Cassandra 4.x. Earlier versions of Cassandra only work with Java 8.

You can't use connector compiled for Scala 2.11 with Spark 3.2.0 that is compiled with Scala 2.12. You need to use appropriate version - right now it's 3.1.0 with coordinates com.datastax.spark:spark-cassandra-connector_2.12:3.1.0

P.S. Please note that although basic functionality will work, more advanced functionality won't work until the SPARKC-670 is fixed (see this PR)