Change in Maven group ID for cassandra-java-driver #15147
Description
Is your feature request related to a problem? Please describe.
Starting from cassandra-java-driver 4.18, the driver was donated from DataStax to the Apache Foundation, and now it is maintained by the Apache Foundation. Because of this change, the maven group id has been changed from com.datastax.oss to org.apache.cassandra.
Due to the changed maven group id, OpenTelemetry Java instrumentation fails the muzzle check, and cassandra sessions are not instrumented anymore after 4.18.
Describe the solution you'd like
Comparing cassandra-4.4 to cassandra-4.18, the public interface of cassandra-4.18 is almost same as cassandra-4.4, and the instrumentation could work if the org.apache.cassandra maven group id is added to the muzzle in the build.gradle of cassandra-4.4.
However, since the driver version and maven group id are different, it is better to add new instrumentation for cassandra-4.18.
If the instrumentation for cassandra-4.18 is added, its logic will be almost same as the instrumentation for cassandra-4.4, because the public interface of the target class and method is not changed.
But shared modules cannot be extracted, since each driver depends on different dependency and maven group id.
We need to add new instrumentation which has almost same logic with cassandra-4.4.
The dependency should be set to org.apache.cassandra:java-driver-core,
and the muzzle group id should be configured as org.apache.cassandra.
Describe alternatives you've considered
No response
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.