Skip to content

Conversation

mkorolyov
Copy link

ScyllaDB is a drop in more performant replacement for Cassandra. It works out of the box with GeoMesa just by replacing connection string from Cassandra to ScyllaDB. Lets mention this in docs so people will be aware of such option.

@elahrvivaz
Copy link
Contributor

Thanks for adding the docs! I don't think we should replace all mentions of Cassandra with Cassandra/ScyllaDB - how about adding a new scylladb/index.rst file that comes after Cassandra and just says that the Cassandra store is also compatible with ScyllaDB? And if there are any differences (e.g. /etc/scylla/scylla.yaml for config), call them out there.

@mkorolyov mkorolyov force-pushed the GEOMESA-3435-add-scylladb-to-docs branch from 392150f to 6675d5a Compare February 2, 2025 20:58
@mkorolyov mkorolyov requested a review from elahrvivaz February 2, 2025 20:59
@elahrvivaz
Copy link
Contributor

changes look reasonable to me, but the build is failing. @jnh5y do you have any comments?

@mkorolyov
Copy link
Author

@elahrvivaz Hey, build fixed, could you pls take a look one more time?

@jnh5y
Copy link
Contributor

jnh5y commented Mar 6, 2025

@mkorolyov thanks for adding the test containers; it is a huge help to be able to test things over time!

@elahrvivaz The changes look reasonable to me. As soon as we get a green build, I'd say it is good to go. I kicked off the build...

I see some codacy things failed; I don't understand it.

Comment on lines 56 to 63
<version>1.20.4</version>
<scope>test</scope>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<version>1.20.4</version>
<scope>test</scope>

we can leave these out since they're defined in the main pom dependency management. Do we need 1.20.4? currently we're on 1.20.3 - it's fine to bump it, we'd just want to do it in the main pom.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated in the main pom to 1.20.6(the latest one) We need 1.20.5+ to recently added ScyllaDB Container support in java test containers

Comment on lines +46 to +49
cassandraContainer.start()
scyllaContainer.start()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tests are failing to connect to the container - i think you'd have to add exposed ports for 9042 here, and then use container.getMappedPort(9042) in the data store params

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i've migrated from Generic container where we need to handle such things explicitly to CassandraContainer and ScyllaDBContainer, which handles such things out of the box. Could you pls retry the tests?

@elahrvivaz
Copy link
Contributor

the codacy failure just needed a retry, and the dash failures are b/c i opened some eclipse tickets that are in an "open" unresolved state, so no worries there.

@mkorolyov mkorolyov force-pushed the GEOMESA-3435-add-scylladb-to-docs branch from 168d7ce to 07b0818 Compare March 8, 2025 15:35
@mkorolyov mkorolyov force-pushed the GEOMESA-3435-add-scylladb-to-docs branch from 07b0818 to 5a3c128 Compare March 8, 2025 15:39
@mkorolyov mkorolyov requested a review from elahrvivaz March 8, 2025 15:40
params = Map(
Params.ContactPointParam.getName -> s"$host:$port",
val params = Map(
Params.ContactPointParam.getName -> s"${container.getHost}:9042",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think you're still going to need container.getMappedPort(0942) (syntax might be wrong...) here and above, otherwise both containers are going to conflict on that port.

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