You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
Steps to reproduce
Upgrade ES to version 9.
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
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
The text was updated successfully, but these errors were encountered:
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?
Steps to reproduce
Expected behavior
Query executes as expected.
Relevant log output
Screenshot
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
The text was updated successfully, but these errors were encountered: