Cassandra requirements and prerequisites
Support matrix
Refer to the below support matrix to ensure compatibility between the platform, database, connector, and Delphix engine version.
Color | Supported? |
Y | Yes |
N | No |
Database / OS support matrix
Supported OS Version | Supported DBMS Versions | |||
DataStax Cassandra v5.1.16 | DataStax Cassandra v6.8.9 - v6.8.33 | Apache Cassandra v3.11.10 | Apache Cassandra v4.0.7 - v4.1.1 | |
RHEL 7.4 | Y | Y | Y | Y |
RHEL 7.9 | Y | Y | Y | Y |
RHEL 8.0 | Y | Y | Y | Y |
Windows | N | N | N | N |
Supported ingestion matrix
Cassandra Distribution | Staging Push | Disk | AWS |
DataStax Enterprise | Y | N | N |
Open-Source Apache | Y | N | N |
Engine compatibility matrix
Engine Version | Cassandra v1.0.0 | Cassandra v1.1.0 | Cassandra v1.1.1 | Cassandra v1.2.0 |
6.0.16.0 - 22.x | Y | Y | Y | Y |
Limitations
Cassandra Ingestion from AWS S3, Disk not supported.
Cassandra Point-in-time restore is not supported.
Delphix V2P is not supported.
Delphix Password Vault is not supported.
Cassandra LDAP Authentication is not supported.
dSource is limited to a single host. A single host can host up to 9 instances (The host needs to be sized appropriately to handle 3-9 Cassandra instances based on requirements).
VDB is limited to max 9 nodes in the cluster. Unlike dSource, VDB can use 9 different hosts for each instance.
Data size is limited to what can be handled by 9 nodes. At present, only small clusters (1-2TB per node with a max of 9 nodes = 9-18 TB per Cluster) can be supported.
dSource node numbers cannot be altered once defined without reloading data.
VDB node numbers cannot be altered once defined without VDB refresh.
Remote Keystore is not supported for SSL Encryption.