andrii-kysylevskyi opened a new issue, #24924: URL: https://github.com/apache/pulsar/issues/24924
### Search before reporting - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation ScyllaDB is a drop-in, more performance-focused replacement for Apache Cassandra. It works out of the box with Pulsar simply by replacing the Cassandra connection string with a ScyllaDB one in the liquibase-cassandra extension (verified this locally) There are already some articles on integrating Pulsar with Scylla [here](https://www.scylladb.com/2022/04/25/streaming-real-time-chat-messages-into-scylladb-with-apache-pulsar/) and [here](https://www.scylladb.com/2023/05/15/tencent-games-real-time-event-driven-analytics-system-built-with-scylladb-pulsar/). So it might be worth solidifying this in Pulsar's docs and tests. ### Solution The suggestion is to: 1. Add a change to README files, pre-integ-tests.sh, and write new tests in the [core repo](https://github.com/apache/pulsar) 2. Add new ScyllaDB documentation in a [documentation repo](https://github.com/apache/pulsar-site) For the new tests, I am thinking something like this: 1. A new `ScyllaDBContainer` class in tests/integration/containers 2. A new ScyllaDBSinkTester in integration/io/sinks (using the same Sink class as Cassandra) 3. New methods in `PulsarSinksTest` - `testScyllaDBSink` and `testScyllaDBArchiveSink` For the documentation, I would suggest: 1. Adding a new section to [this page](https://pulsar.apache.org/docs/4.1.x/io-quickstart/) under the `How to connect Pulsar to database` section 2. Adding a mention of ScyllaDB drop-in replacement on [this page](https://pulsar.apache.org/docs/4.1.x/io-cassandra-sink/), since the same classes used by Cassandra can be used by Scylla I am happy to work on those changes and will submit a PR soon ### Alternatives _No response_ ### Anything else? _No response_ ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
