-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 Elasticsearch v5 / v6 #5439
Closed
3 tasks done
Labels
area/storage
good first issue
Good for beginners
help wanted
Features that maintainers are willing to accept but do not have cycles to implement
storage/elasticsearch
Comments
yurishkuro
added
help wanted
Features that maintainers are willing to accept but do not have cycles to implement
good first issue
Good for beginners
area/storage
storage/elasticsearch
labels
May 11, 2024
yurishkuro
added a commit
that referenced
this issue
May 11, 2024
## Which problem is this PR solving? - Part of #5439 ## Description of the changes - Stop running integration tests for Elasticsearch v5/v6 ## How was this change tested? - CI Signed-off-by: Yuri Shkuro <github@ysh.us>
4 tasks
yurishkuro
pushed a commit
to jaegertracing/documentation
that referenced
this issue
May 12, 2024
## Which problem is this PR solving? - Relate jaegertracing/jaeger#5439 ## Description of the changes - Remove ElasticSearch 5.x & 6.x documentation ## How was this change tested? - Manual ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [ ] I have added unit tests for the new functionality - [ ] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `yarn lint` and `yarn test` Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com>
This was referenced May 13, 2024
yurishkuro
pushed a commit
that referenced
this issue
May 13, 2024
## Which problem is this PR solving? - Resolves second point in the checklist of #5439 ## Description of the changes - Removed support for Elasticsearch v5/v6 in mapping.go and mapping_test.go ## How was this change tested? - ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [ ] I have added unit tests for the new functionality - [ ] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `yarn lint` and `yarn test` --------- Signed-off-by: FlamingSaint <raghuramkannan400@gmail.com>
4 tasks
vinayakjaas
added a commit
to vinayakjaas/jaeger
that referenced
this issue
May 27, 2024
Signed-off-by: vinayakjaas <vinayakrajqaz@gmail.com>
4 tasks
yurishkuro
pushed a commit
that referenced
this issue
May 27, 2024
varshith257
pushed a commit
to varshith257/jaeger
that referenced
this issue
Jun 2, 2024
…tracing#5491) Signed-off-by: Vamshi Maskuri <gwcchintu@gmail.com>
yurishkuro
added a commit
that referenced
this issue
Jul 4, 2024
Reverts parts of #5439 Motivation: some vendors still provide commercial support for ES v6 to customers, even though ESv6 EOL was Nov 2020. --------- Signed-off-by: Pavol Loffay <p.loffay@gmail.com> Signed-off-by: Yuri Shkuro <github@ysh.us> Co-authored-by: Yuri Shkuro <github@ysh.us>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/storage
good first issue
Good for beginners
help wanted
Features that maintainers are willing to accept but do not have cycles to implement
storage/elasticsearch
According to https://endoflife.date/elasticsearch, ESv6 reached EOL in 2022 (no data for ESv5, presumably even earlier).
The text was updated successfully, but these errors were encountered: