Skip to content

[Bug]: Elasticsearch 9 Range Query Deprecated Parameters #7150

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

Open
bnbillings-skillsoft opened this issue May 20, 2025 · 1 comment
Open

Comments

@bnbillings-skillsoft
Copy link

What happened?

Running jaeger-query in kubernetes (version 1.62), and we just upgraded our backend ES cluster to version 9.0.1. Jaeger trace queries are now broken due to range query params that are deprecated. Also, after digging through the code i noticed that Jaeger does not use the official elasticsearch go client, its instead using a deprecated client from "olivere" that hasnt been updated in over 3 years. So im curious is there any plan to support ES version 9, and where is that on the roadmap?

Image

Image

Steps to reproduce

  1. Upgrade ES to version 9.
  2. Run any trace query from the UI.

Expected behavior

Query executes as expected.

Relevant log output

HTTP Error: search services failed: elastic: Error 400 (Bad Request): [1:221] [bool] failed to parse field [must] [type=x_content_parse_exception]: RootCause[[range] query does not support [from] [type=parsing_exception]]: RootCause[[range] query does not support [from] [type=parsing_exception]]

Screenshot

Image
Image

Additional context

No response

Jaeger backend version

No response

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

No response

Deployment model

No response

Deployment configs

@yurishkuro
Copy link
Member

we could try it as Fall LFX mentorship project, as part of #4708

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

No branches or pull requests

2 participants