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

[Deprecation] Drop support for Cassandra 3.x #5160

Closed
yurishkuro opened this issue Feb 3, 2024 · 6 comments · Fixed by jaegertracing/documentation#742
Closed

[Deprecation] Drop support for Cassandra 3.x #5160

yurishkuro opened this issue Feb 3, 2024 · 6 comments · Fixed by jaegertracing/documentation#742

Comments

@yurishkuro
Copy link
Member

3.x is declared EOL https://cassandra.apache.org/_/blog/Apache-Cassandra-3.0.x-and-3.11.x-End-of-Life-Announcement.html

According to https://cassandra.apache.org/_/download.html, support for it will end once 5.x is released, which was aimed ad Dec'23, but as of 2023-12-05 only 5-Beta was released. In any case, I expect by summer 2024 the 3.x support will end, and we should remove it from Jaeger as well.

This doesn't remove any implementation, only the CI testing can drop testing with 3.x (and we should add testing with 5.x. once it is released).

@yurishkuro yurishkuro added help wanted Features that maintainers are willing to accept but do not have cycles to implement good first issue Good for beginners and removed help wanted Features that maintainers are willing to accept but do not have cycles to implement good first issue Good for beginners labels Apr 21, 2024
@varshith257
Copy link
Contributor

It seems Cassandra 5.0 had released. Am I right @yurishkuro ?

@yurishkuro
Copy link
Member Author

do you have a link?

@yurishkuro
Copy link
Member Author

I don't see much change: Apache Cassandra 5.0-beta Latest release on 2023-12-05

I.e. no official release.

@mahadzaryab1
Copy link
Collaborator

@yurishkuro PR up for review at #5962

yurishkuro pushed a commit that referenced this issue Sep 10, 2024
## Which problem is this PR solving?
-  Part of #5160 

## Description of the changes
- Deprecated Cassandra 3.x as it was marked EOL
- Enabled CI testing and schema generation for 5.x which GA-ed on 09/05
(https://cassandra.apache.org/_/download.html)

## How was this change tested?
- CI

## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [x] I have added unit tests for the new functionality
- [x] I have run lint and test steps successfully
  - for `jaeger`: `make lint test`
  - for `jaeger-ui`: `yarn lint` and `yarn test`

---------

Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
@mahadzaryab1
Copy link
Collaborator

PR for documentation up for review at jaegertracing/documentation#742

@yurishkuro
Copy link
Member Author

🎉

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

Successfully merging a pull request may close this issue.

3 participants