Jaeger compatibility with AWS Opensearch 3.1 version

[gartemiev]

We upgraded our Amazon OpenSearch domain to engine 3.1.

Our tracing backend is Jaeger. Jaeger supports Elasticsearch 7.x and 8.x, and historically also worked with OpenSearch 1.x/2.x.
See:
https://www.jaegertracing.io/docs/2.11/storage/opensearch/
https://www.jaegertracing.io/docs/2.11/storage/elasticsearch/

After the upgrade, the domain’s root endpoint reports version 7.10.2 (due to enabled compatibility mode). We need to confirm whether AWS OpenSearch 3.1 is fully supported/compatible with Jaeger, and whether the reported version is only a facade for client compatibility or implies older wire/index semantics.

Cluster details are:
{ "name": "46f330d06209860f30b7a9693084adc0", "cluster_name": "497854349903:nonprod-tracing-os", "cluster_uuid": "dkC6zgMxRRS3-MSLZWJJjQ", "version": { "number": "7.10.2", "build_type": "tar", "build_hash": "unknown", "build_date": "2025-10-02T02:20:25.196856080Z", "build_snapshot": false, "lucene_version": "10.2.1", "minimum_wire_compatibility_version": "2.19.0", "minimum_index_compatibility_version": "2.0.0" }, "tagline": "The OpenSearch Project: https://opensearch.org/" }

[dosubot[bot]]

Hi @gartemiev! I'm Dosu and I’m helping the jaeger team.

Jaeger does not officially support OpenSearch 3.x yet, and there are open feature requests and ongoing work to address compatibility issues with this version issue #7133 issue #7119. However, Jaeger's source code explicitly detects OpenSearch 3.x (including AWS OpenSearch 3.1) and internally treats it as Elasticsearch 7.x for index mappings and wire protocol compatibility. This means the reported version (7.10.2) is primarily a facade for client compatibility, and Jaeger will use ES 7.x semantics for storage operations config.go cluster_client.go.

Known issues include operational quirks with AWS endpoints, authentication, and health checks, but there are no protocol-level or index mapping incompatibilities from Jaeger's perspective. If you encounter problems, they are likely due to AWS-specific behaviors rather than Jaeger's wire or index logic.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[yurishkuro]

Our integration tests run against 3.2

https://github.com/jaegertracing/jaeger/blob/main/docker-compose/opensearch/v3/docker-compose.yml#L3