Skip to content
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.

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

[Feature Request] Provide 4.1.4+ Cassandra support #144

Open
Subetov opened this issue Apr 9, 2024 · 6 comments
Open

[Feature Request] Provide 4.1.4+ Cassandra support #144

Subetov opened this issue Apr 9, 2024 · 6 comments

Comments

@Subetov
Copy link

Subetov commented Apr 9, 2024

Feature Request

Please provide 4.1.4+ Cassandra support.

@Subetov Subetov changed the title Provide 4.1.4+ Cassandra support [Feature Request] Provide 4.1.4+ Cassandra support Apr 9, 2024
@cscetbon
Copy link
Owner

@AKamyshnikova Can you tell me if 4+ needs some work here ? I saw 5.0 is out so no matter what we'll have some work to add its support

@AKamyshnikova
Copy link
Collaborator

@cscetbon casskop seems to work fine with 4.1.6 (just checked) So, seems the multicasskop required some work with 4+ versions.

@cscetbon
Copy link
Owner

cscetbon commented Sep 16, 2024

Hopefully upgrading to 5+ as well won't require much work in casskop and only on multicasskop as well. Not sure why though ...

@mzylowski
Copy link
Contributor

It looks like there is a problem with missing support for Cassandra.yaml for 4.1.x (there were a lot of changes around configuration fields) in DataStax; see datastax/cass-config-builder#61. This causes issues with provisioning correct cassandra.yaml for 4.1.x cassandra deployed by casskop.

@cscetbon
Copy link
Owner

In the meantime you can always use a pre-run script to update cassandra.yaml if it doesn't do what is expected. But yeah we heavily rely on cass-config-builder to generate the configuration and as far as I know they've been updating it only for DSE, so if you want to create a PR to get fixed don't hesitate and we can update the version we use here. If it isn't feasible we'll have to fork the project.

@cscetbon
Copy link
Owner

cscetbon commented Dec 2, 2024

@Subetov 👆

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

No branches or pull requests

4 participants