Skip to content

Conversation

@pjfanning
Copy link
Member

instead of cassandra-launcher that uses a very old version of Cassandra and that it would be great to get rid of

@pjfanning pjfanning marked this pull request as draft October 24, 2025 17:41
@raboof
Copy link
Member

raboof commented Nov 7, 2025

this looks great and CI is green, any reason this is still 'draft'?

@pjfanning
Copy link
Member Author

@raboof I'm having trouble running Cassandra via Docker on my old laptop. If you or someone else has time to run one or more of the samples on their own machines then that would be appreciated.

@raboof
Copy link
Member

raboof commented Nov 7, 2025

Ah, and this is not covered by CI of course, pity.

@samueleresca
Copy link
Member

If you or someone else has time to run one or more of the samples on their own machines, then that would be appreciated.

I'm taking a look at this. pekko-sample-distributed-workers-scala and pekko-sample-persistence-dc-scala seem not to be working properly. My understanding is that CassandraLauncher does stuff on top of running Cassandra. Also, it is not running Cassandra as a separate container.

I'm taking a look at this. I'm wondering if it is cheaper to just upgrade Cassandra in the cassandra-launcher module

@pjfanning
Copy link
Member Author

@samueleresca I've attempted to upgrade cassandra in the launcher but with little luck

And since the old cassandra version doesn't work in Java 17, it is blocking progress for v2.

The launcher does not seem to much more than start cassandra for you. I think the ideal is to remove it but if we must keep it then we'll have to put up with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants