[
https://issues.apache.org/jira/browse/CASSANDRASC-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166660#comment-17166660
]
ASF subversion and git services commented on CASSANDRASC-23:
------------------------------------------------------------
Commit a4805a910904019698ae373ac33f88855cf67f3d in cassandra-sidecar's branch
refs/heads/master from Jon Haddad
[ https://gitbox.apache.org/repos/asf?p=cassandra-sidecar.git;h=a4805a9 ]
Support for multiple Cassandra versions
This patch lays the groundwork to support multiple Cassandra versions.
New submodules were created for common libraries as well as specific
Cassandra versions. Several dependencies are moved to the common
submodule due to their universal nature.
Most importantly, this patch introduces Junit Test Template for testing multiple
Cassandra versions. Test should be annotated with a
@CassandraIntegrationTest. These tests require Docker and Kubernetes be
available.
A single version is currently supported, 4.0. A dockerfile sets up the image
from the beta tarball and initializes the session.
Cassandra driver was upgraded to version 3.9, previous versions errored
with Java 11.
CircleCI tests are run using microk8s.
Patch by Jon Haddad; Reviewed by Dinesh Joshi for CASSANDRASC-23
> Set up structure for handling multiple Cassandra versions
> ---------------------------------------------------------
>
> Key: CASSANDRASC-23
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-23
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
> Reporter: Jon Haddad
> Assignee: Jon Haddad
> Priority: Normal
>
> The first sidecar release will be for Cassandra 4.0, but one of the project
> goals is to be able to handle multiple versions. This will be especially
> important in mixed version clusters, or even mixed version 1:N sidecar to C*
> nodes (see CASSANDRASC-17).
> This JIRA is to lay the foundational work for supporting multiple Cassandra
> versions.
> Each Cassandra version (for example \{{cassandra40}}, \{{cassandra50}}, will
> be in a separate Gradle subproject, implementing a common interface defined
> in a \{{common}} subproject. A common cassandra integration testing
> framework will be able to test every version to ensure each version adheres
> to the expected interface.
> Each module will define the minimum compatibility it supports, so if someone
> (for example) wants to implement a Cassandra30 module for their own cluster,
> they will have the ability to do so.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
