Skip to content

docs: bump luna version and remove pulsar version #213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 5, 2025
Merged

docs: bump luna version and remove pulsar version #213

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/antora.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,5 @@ asciidoc:
csc_pulsar_first: 'DataStax Cassandra Source Connector for Apache Pulsar(TM)'
csc_pulsar: 'CSC for Pulsar'
cdc_pulsar: 'CDC for Cassandra'
luna_version: '2.10'
pulsar_version: '2.10'
luna_version: '3.1'
version: '2.3.2' # cdc-apache-cassandra latest {version}
4 changes: 2 additions & 2 deletions docs/modules/ROOT/pages/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ For each update to the table, an MD5 digest is calculated to de-duplicate the up
== Supported streaming platforms

* IBM Elite Support for Apache Pulsar (formerly DataStax Luna Streaming) 2.8 and later (current version is {luna_version})
* Apache Pulsar 2.8.1 and later (current Pulsar version is {pulsar_version})
* Apache Pulsar 2.8.1 and later

=== Connector deployment matrix

Expand Down Expand Up @@ -158,5 +158,5 @@ To ensure the data sent to all datacenters are delivered to the data topic, make

For example, given a Cassandra cluster with three datacenters (DC1, DC2, and DC3), you would enable CDC and install the change agent in only DC1.
To ensure all updates in DC2 and DC3 are propagated to the data topic, configure the table's keyspace to replicate data from DC2 and DC3 to DC1.
For example, `replication = {'class': 'NetworkTopologyStrategy', 'dc1': 3, 'dc2': 3, 'dc3': 3})`.
For example, `replication = {'class': 'NetworkTopologyStrategy', 'dc1': 3, 'dc2': 3, 'dc3': 3}`.
The data replicated to DC1 will be processed by the change agent and eventually end up in the data topic.