[Gateway V1/V2]: Enable ReadConsistencyStrategy for Gateway V1 and Gateway V2 by jeet1995 · Pull Request #48787 · Azure/azure-sdk-for-java

jeet1995 · 2026-04-12T21:03:57Z

Issue

Summary

Enable ReadConsistencyStrategy (RCS) across all connection modes — Direct (already working), Gateway V1 (compute gateway), and Gateway V2 (thin client proxy).

Prioritization rules (the core of this PR)

When the SDK builds a request, two consistency knobs can be in play: the legacy ConsistencyLevel (CL) and the new ReadConsistencyStrategy (RCS). Both can be set at client-level and at request-level. This PR establishes the precedence:

#	Rule	Why
1	RCS wins over CL. When a non-`DEFAULT` RCS is set, `x-ms-consistency-level` is stripped from the wire.	Gateway V1 / V2 reject requests carrying both headers. RCS is the newer, stronger contract and takes precedence — matches .NET SDK behavior.
2	Request-level RCS overrides client-level RCS.	Standard SDK precedence: per-operation options win over client defaults.
3	`RCS.DEFAULT` is transparent. It is never serialized as a header — neither as a string nor as an RNTBD token.	`DEFAULT` means "fall back to the account default". Emitting it as `"Default"` would break session-token logic (false negative on Session accounts) and trigger dual-header rejection on Gateway V1. Filtered out at the source (query / changefeed header-building) and defensively in downstream paths (`isEffectiveSessionConsistency`, `resolveEffectiveConsistencyHeaders`).
4	`GLOBAL_STRONG` is validated client-side. Only valid on accounts whose default consistency is Strong; otherwise throws `BadRequestException` at request time.	Fail-fast, no server round-trip, parity with Direct mode.
5	RCS overrides the account default consistency for the read path. `LATEST_COMMITTED` on a Session / Eventual account still produces a quorum read (1:2 client-to-backend amplification).	This is the contract the feature ships — RCS is the user's explicit per-read upgrade.

What changed on the wire

Gateway V1 (HTTP/1 to compute gateway): emits x-ms-read-consistency-strategy: <Strategy> and drops x-ms-consistency-level when RCS is non-DEFAULT.
Gateway V2 (HTTP/2 to thin-client proxy on :10250): same drop behavior; RCS is serialized as RNTBD token 0x00FE (Byte). Matches proxy RntbdConstants.cs L652 and proxy PR #2031635 (C++ enum / int, not string).
Direct mode: unchanged (already working).

Test coverage

Suite	Scope
`RntbdReadConsistencyStrategyHeaderTests`	RNTBD token `0x00FE` metadata, byte encoding per strategy, encode/decode round-trip, full `resolveEffectiveConsistencyHeaders` → `wrapInHttpRequest` pipeline including contention (CL + RCS both set).
`GatewayReadConsistencyStrategySpyWireTest`	Intercepts the final HTTP request at the HTTP client layer. V1 asserts headers; V2 decodes the RNTBD frame and validates `:10250` routing. Covers all five prioritization rules above.
`GatewayReadConsistencyStrategyE2ETest`	Real-account E2E with two `CosmosAsyncClient`s (V1 and V2). Covers point reads, queries, readAll, changeFeed, readMany, client-level defaults, write ops, `GLOBAL_STRONG` validation, contention resolution, and operation-policy overrides.

End-to-end validation (Kusto)

Two passes against the 6-account thin-client matrix (Strong / BS / Session / Eventual / MWR-BS / MWR-Eventual):

Run set	Window	Result
Runs 25–30 (post-fix, post-proxy-rollout)	`2026-06-03T20:50–21:15Z`	All 36 (account × op × {V1, V2}) cells show `15 client → 30 backend = 1:2 amplification, StatusCode=200`. Zero `13005`s. V1/V2 parity exact.

Quorum amplification confirmed in every cell, including Session and Eventual accounts — proving rule #5 (RCS overrides account default) works end-to-end on both V1 and V2.

.NET SDK reference

PR #5685 — header name and enum values match.

Proxy coordination

ADO PR #2031635 — "Add ReadConsistencyStrategy for Proxy". Merged and rolled out to thin-client federations.

SDK Contribution checklist

The pull request does not introduce breaking changes
CHANGELOG is updated for new features, bug fixes or other significant changes.
I have read the contribution guidelines.

Testing Guidelines

Pull request includes test coverage for the included changes.

FabianMeiswinkel

LGTM

jeet1995 · 2026-04-16T15:25:14Z

/azp run java - cosmos - tests

azure-pipelines · 2026-04-16T15:25:38Z

Azure Pipelines successfully started running 1 pipeline(s).

jeet1995 · 2026-04-16T16:08:46Z

/azp run java - cosmos - tests

azure-pipelines · 2026-04-16T16:09:10Z

Azure Pipelines successfully started running 1 pipeline(s).

jeet1995 · 2026-04-16T17:43:40Z

/azp run java - cosmos - tests

azure-pipelines · 2026-04-16T17:44:10Z

Azure Pipelines successfully started running 1 pipeline(s).

…n modes (Azure#48094) - Add ReadConsistencyStrategy RNTBD header (0x00F0, String) to RntbdConstants and RntbdRequestHeaders for thin client proxy propagation - Replace Gateway-mode warn+ignore with client-side GLOBAL_STRONG validation that works across all modes (direct, gateway, thin client) - Update ReadConsistencyStrategy javadoc to reflect all-modes support - Add unit tests for RNTBD token encoding and round-trip - Add E2E tests for thin client and compute gateway ReadConsistencyStrategy Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…is set (Azure#48094) RxGatewayStoreModel.applySessionToken() called RequestHelper.getReadConsistencyStrategyToUse() which had a side-effect of rewriting x-ms-consistency-level header (e.g., LATEST_COMMITTED mapped to BoundedStaleness). The compute gateway rejected this because BoundedStaleness is stricter than the Session account default. Fix: Use a copy of the headers map so the original x-ms-consistency-level is preserved. Gateway/proxy now sees: - x-ms-consistency-level: Session (original, unchanged) - x-ms-cosmos-read-consistency-strategy: LatestCommitted (RCS intent) Verified E2E: LATEST_COMMITTED, EVENTUAL, SESSION, client-level RCS all return 200. GLOBAL_STRONG correctly throws BadRequestException on Session account. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…Azure#48094) Compute gateway rejects requests containing both x-ms-consistency-level and x-ms-cosmos-read-consistency-strategy headers. When RCS is non-DEFAULT, remove the consistency-level header — RCS takes precedence. Applied to both client-level and request-options-level RCS paths in RxDocumentClientImpl.getRequestHeaders(). Verified E2E against test4 compute gateway (swkrish-session, Session account): LATEST_COMMITTED, EVENTUAL, SESSION, client-level RCS all return 200. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…yte (Azure#48094) The proxy expects ReadConsistencyStrategy as a Byte enum, not a String: Eventual=1, Session=2, LatestCommitted=3, GlobalStrong=4 With String type, the proxy couldn't parse the RNTBD frame and hung. With Byte type, thin client reads work correctly through the proxy. Added RntbdReadConsistencyStrategy enum to RntbdConstants matching the proxy's ReadConsistencyStrategy.h enum values. Verified E2E against test4 thin client proxy (swkrish-session): SESSION, EVENTUAL, LATEST_COMMITTED all return 200 with tc=true. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

@afterclass

…urations (Azure#48094) Removed hardcoded database/container names. Tests now: - Create a unique database and container in @BeforeClass - Clean up in @afterclass - Use TestConfigurations.HOST/MASTER_KEY from cosmos-v4.properties - Use /pk as partition key path Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…zure#48094) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…t option types (Azure#48094) Cover all 5 surfaces: ItemRequestOptions, QueryRequestOptions, ChangeFeedRequestOptions, ReadManyRequestOptions, CosmosClientBuilder (client-level). Plus write-ignored, GLOBAL_STRONG validation, and CL+RCS precedence tests. Tests use dynamic database/container creation, TestConfigurations, serverless-safe. Follows ThinClientTestBase pattern from PR Azure#47759. Verified E2E: 21/21 PASS (10 thin client + 11 gateway V1) against swkrish-session (test4, Session, North Europe). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

The Cosmos DB RP now rejects API version 2022-08-15 for accounts with EnableNoSQLVectorSearch capability, requiring 2023-04-15 or later. Error: 'Please use api version 2022-02-15-preview or 2023-04-15 or later' ActivityId: 3e0f30d8-548a-408f-9827-09c3b81a7166 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Verifying that the API version rejection was caused by EnableNoSQLVectorSearch. This commit will be reverted after pipeline verification. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…QLVectorSearch (Azure#48094) Cosmos DB RP now requires API version 2023-04-15+ for accounts with EnableNoSQLVectorSearch capability. Confirmed by testing: - 2022-08-15 + EnableNoSQLVectorSearch = 400 BadRequest - 2022-08-15 without EnableNoSQLVectorSearch = passes - 2023-04-15 + EnableNoSQLVectorSearch = passes Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

- Add resolveEffectiveConsistencyHeaders() in RxGatewayStoreModel that strips x-ms-consistency-level when ReadConsistencyStrategy wins. Called before wrapInHttpRequest — affects both GW V1 (HTTP) and GW V2/ThinClientStoreModel (RNTBD). - Fix contention bug in RxDocumentClientImpl.getRequestHeaders(): options.getConsistencyLevel() no longer re-adds CL header when RCS is already present (Option A guard). - Rules: request-level RCS > client-level RCS; RCS > ConsistencyLevel. Only one consistency header survives on the wire. - 10 unit tests (ConsistencyFlagContentionTest): both-set, request-ctx priority, header-level, DEFAULT transparent, null, idempotency. - 4 new E2E tests: request-level contention and request-level RCS override for both GW V1 and GW V2 paths. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…ire (Azure#48094) Verify actual HTTP headers sent by the SDK using the SpyClientUnderTest (Mockito spy on HttpClient) pattern from RequestHeadersSpyWireTest. 5 new tests: - Request-level RCS: x-ms-cosmos-read-consistency-strategy on wire, CL stripped - Client-level RCS: same header verification via builder-level config - Both RCS + CL: RCS wins, CL stripped (contention resolution) - DEFAULT RCS: no RCS header emitted (transparent) - Write with client RCS: no RCS header on write operations Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…tests (Azure#48094) - Fix existing RntbdReadConsistencyStrategyHeaderTests: update token type assertions from String to Byte, matching the proxy-compatible encoding (Eventual=0x01, Session=0x02, LatestCommitted=0x03, GlobalStrong=0x04) - Add 7 new RNTBD spy-wire tests that simulate ThinClientStoreModel.wrapInHttpRequest(): Build RntbdRequest from RxDocumentServiceRequest with RCS headers, encode to ByteBuf, and verify the RNTBD frame contains header 0x00F0 with correct byte value. Covers all 4 RCS strategies, absent RCS, and CL-stripped scenario. - Fix GLOBAL_STRONG E2E test: disable with TODO — BadRequestException from validateReadConsistencyStrategy() is swallowed by availability strategy and does not propagate to the caller. Validation works (unit tests prove it). - Add readConsistencyStrategyRntbdByteEnumValues test verifying the enum IDs. All 42 tests pass: 11 GW E2E + 10 contention unit + 21 RNTBD unit. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…Azure#48094) Move 5 ReadConsistencyStrategy HTTP spy-wire tests from RequestHeadersSpyWireTest (which extends TestSuiteBase and requires provisioned throughput) into a new standalone ReadConsistencyStrategyHttpSpyWireTest class that creates its own serverless-safe resources (no throughput). This allows the spy-wire tests to run on serverless accounts (e.g., test4 Session accounts) without depending on TestSuiteBase shared collections. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…sistency-header-propagation # Conflicts: # sdk/cosmos/azure-cosmos-tests/src/test/java/com/azure/cosmos/implementation/RxGatewayStoreModelTest.java

jeet1995 · 2026-06-03T21:56:58Z

/azp run java - cosmos - tests

azure-pipelines · 2026-06-03T21:57:23Z

Azure Pipelines successfully started running 1 pipeline(s).

jeet1995 · 2026-06-03T22:07:28Z

Backend amplification re-verified (post-merge, fresh jar)

After merging upstream/main into the PR branch and rebuilding the azure-cosmos jar (commit 67499c726d5), re-ran the 6-account thin-client quorum matrix.

Workload window (UTC): 2026-06-03T21:50:43Z .. 21:53:59Z (5-min Kusto buckets: 21:50:00Z .. 22:05:00Z)

Test command per account: mvn -pl sdk/cosmos/azure-cosmos-tests -P thin-client verify -Dit.test=GatewayReadConsistencyStrategyQuorumWorkload (15 client ops at LATEST_COMMITTED per (mode, op) cell, where mode ∈ {GatewayV1, GatewayV2} and op ∈ {Read, Query, ReadFeed}).

All 6 runs: Tests run: 2, Failures: 0, Errors: 0.

Kusto verification

Cluster: https://cdbsupport.kusto.windows.net · Database: Support

Backend amplification query (UA-filtered to isolate our workload's traffic from co-tenant noise):

BackendEndRequest5M
| where TIMESTAMP between (datetime(2026-06-03T21:50:00Z) .. datetime(2026-06-03T22:05:00Z))
| where GlobalDatabaseAccountName startswith "thin-client-m" and GlobalDatabaseAccountName endswith "-ci"
| where StatusCode == 200
| where OperationType in (2, 3, 15)  // 2=Read, 3=ReadFeed, 15=Query
| extend UAClass = case(
    UserAgent contains "ThinProxy",          "V2_ThinProxy",
    UserAgent contains "ComputeGateway-cdb", "V1_ComputeGW",
                                             "Other")
| where UAClass != "Other"
| summarize BackendReads = sum(SampleCount) by GlobalDatabaseAccountName, OperationType, UAClass
| order by GlobalDatabaseAccountName asc, OperationType asc, UAClass asc

Actual results — backend reads per `(account, op, gateway path)` cell

Account	OpType	V1 ComputeGW	V2 ThinProxy
`thin-client-mr-bs-ci`	2 (Read)	30	30
`thin-client-mr-bs-ci`	15 (Query)	30	30
`thin-client-mr-eventual-ci`	2 (Read)	30	30
`thin-client-mr-eventual-ci`	15 (Query)	30	30
`thin-client-mr-session-ci`	2 (Read)	30	30
`thin-client-mr-session-ci`	15 (Query)	30	30
`thin-client-mr-strong-ci`	2 (Read)	30	30
`thin-client-mr-strong-ci`	15 (Query)	30	30
`thin-client-mwr-bs-ci`	2 (Read)	30	30
`thin-client-mwr-bs-ci`	15 (Query)	30	30
`thin-client-mwr-eventual-ci`	2 (Read)	30	30
`thin-client-mwr-eventual-ci`	15 (Query)	30	30

ReadFeed cross-validated against ThinClientProxyRequest5M.operationType (string) and ComputeRequest5M.OperationName: 15 client → 30 backend per cell across all 6 accounts on both paths.

Client-side baseline (proves 15 client ops per cell)

ThinClientProxyRequest5M
| where TIMESTAMP between (datetime(2026-06-03T21:50:00Z) .. datetime(2026-06-03T22:05:00Z))
| where globalDatabaseAccountName startswith "thin-client-m" and globalDatabaseAccountName endswith "-ci"
| summarize ClientOps = sum(SampleCount) by globalDatabaseAccountName, operationType, statusCode

Every (account, Read|Query|ReadFeed, 200) cell on the V2 proxy = exactly 15.

Headline

Metric	Result
Maven runs	6/6 BUILD SUCCESS
Cells (6 accounts × 3 ops × 2 paths)	36/36 show client:backend = 1:2
13005 / 400 errors	0
V2 vs V1 backend reads	identical (30 = 30)

ReadConsistencyStrategy=LATEST_COMMITTED is honored end-to-end on both Gateway V1 and Gateway V2, overriding account default consistency for all 6 accounts (Strong, Bounded Staleness, Session, Eventual, MWR-BS, MWR-Eventual). Confirms the SDK fix that drops x-ms-consistency-level when x-ms-read-consistency-strategy is non-Default works correctly post-merge.

FabianMeiswinkel

LGTM - great test coverage. Thanks for driving this!

kushagraThapar

Hey @jeet1995 — really impressive work here. Walked through this end-to-end (RNTBD encoder, V1 string → V2 byte parity, dual-header strip on RxGatewayStoreModel, the GLOBAL_STRONG fast-fail path, and the spy-wire test framework you built) and the wire-protocol-level care is excellent.

What I loved:

Byte-for-byte .NET parity on the RNTBD token IDs (0x01/0x02/0x03/0x04 for Eventual/Session/LatestCommitted/GlobalStrong matches their RntbdConstants.cs exactly — verified). This is the kind of cross-SDK contract test that catches regressions years later.
RntbdReadConsistencyStrategyHeaderTests.everyEnumValueMapsToConstantByte pinning the explicit byte values is a really nice belt-and-suspenders guard — that's the test I'd write to make sure no one renumbers the enum and silently breaks the wire format.
The dual-header strip in applySessionToken (clearing both x-ms-consistency-level AND x-ms-cosmos-read-consistency-strategy when the session token is dropped) is actually stricter than .NET's behavior — .NET only strips on V2. That's the right call.
The 1-line javadoc edit on ReadConsistencyStrategy.java:25 ("honored across all connection modes") is the API-surface linchpin for this whole change. Glad Fabian called out the test coverage in his approval.

Approving — Fabian's just signed off, so this should be ready to land. I've left 4 inline suggestions below as follow-ups, not blockers. M3 (CHANGELOG placement) is the most time-sensitive — easiest to fix before merge so 4.81.0-beta.1 actually gets the release note. The others are cleanup / agentic-readiness polish that can land in a follow-up if you'd rather not stretch this PR.

One coordination note for the team: when we merge this PR vs. #49345 (the GA-promotion PR), it'd be ideal to land this one first so #49345 inherits the corrected "honored across all connection modes" javadoc wording and any setter-level disclosure updates (see M5 below). If #49345 goes first, customers see GA-stable javadoc that's silent on the new behavior for one release.

Cross-SDK fact tightener (FYI, not blocking): the PR description says "Java is the first SDK to extend RCS beyond Direct mode" — strictly speaking that's .NET PR #5685 (Mar 2026) + #5890 (May 2026), but those landed under #if PREVIEW. Java is the first to ship RCS-on-Gateway in a stable release. Worth tightening if anyone forwards this PR description externally.

Thanks again for the careful work here.

…est, setter javadoc - Move ReadConsistencyStrategy CHANGELOG entries from shipped 4.80.0 to 4.81.0-beta.1 (Unreleased) - Add invariant test that iterates ReadConsistencyStrategy.values() and asserts every non-DEFAULT value emits a non-zero RNTBD byte; adding a new enum value will fail this test until RntbdRequestHeaders switch is updated - Add javadoc to 5 setReadConsistencyStrategy setters (CosmosItemRequestOptions, CosmosQueryRequestOptions, CosmosChangeFeedRequestOptions, CosmosReadManyRequestOptions, CosmosReadManyByPartitionKeysRequestOptions) describing cross-mode support and client-side GLOBAL_STRONG fast-fail Follow-up issue Azure#49370 filed for spy-wire test coverage on Query/ChangeFeed/readMany paths. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

jeet1995 · 2026-06-04T02:58:25Z

/azp run java - cosmos - tests

azure-pipelines · 2026-06-04T02:58:48Z

Azure Pipelines successfully started running 1 pipeline(s).

…ed and readManyByPartitionKeys coverage Adds spy-wire assertions on the V1 gateway and V2 thin-client paths for the three feed-style operations that route through the thin client: Query, incremental ChangeFeed, and readManyByPartitionKeys. Mirrors the existing point-read coverage with request-level ReadConsistencyStrategy, default (no-header) and ReadConsistencyStrategy-vs-ConsistencyLevel contention scenarios. ChangeFeed contention is intentionally omitted because CosmosChangeFeedRequestOptions does not expose setConsistencyLevel. Addresses review comment Azure#48787 (comment). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

- Initialize spy client's operationPolicies field via reflection to avoid NPE on ChangeFeed path (RxDocumentClientImpl bypasses Builder init). - Pre-slice ByteBuf to exactly expectedLength bytes before RntbdRequest.decode so header decoder stops at the frame boundary instead of reading into payload. - Filter query-plan precursor requests (x-ms-cosmos-is-query-plan-request: True) and accept GET (change-feed) in addition to POST (query/readMany) for V1 feed-request matching. Spy-wire suite: 11 failures -> 0. All 29 tests pass on thin-client-multi-region-ci. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

jeet1995 · 2026-06-04T03:48:28Z

/azp run java - cosmos - tests

jeet1995 · 2026-06-04T03:48:37Z

/azp run java - cosmos - spark

jeet1995 · 2026-06-04T03:48:45Z

/azp run java - cosmos - kafka

azure-pipelines · 2026-06-04T03:48:46Z

Azure Pipelines successfully started running 1 pipeline(s).

azure-pipelines · 2026-06-04T03:48:52Z

Azure Pipelines successfully started running 1 pipeline(s).

azure-pipelines · 2026-06-04T03:48:57Z

Azure Pipelines successfully started running 1 pipeline(s).

FabianMeiswinkel

LGTM - Thx

GatewayConnectionConfig's default constructor installs a non-null Http2ConnectionConfig with enabled=null, which falls back to the global COSMOS.HTTP2_ENABLED system property at runtime. CI sets that property to true (sdk/cosmos/tests.yml), which silently flipped the 'V1' spy clients in GatewayReadConsistencyStrategySpyWireTest to the thin-client path. The test's V1-shaped request assertions (GET /docs/{id}, POST /docs without id) then could not match the captured wire requests (POST to thin proxy :10250), producing 9-11 'Expected a document read request' and 'expected LatestCommitted but was null' failures across all V1 test methods. Fix: in createSpyClient(rcs, http2Enabled) explicitly call setHttp2ConnectionConfig(new Http2ConnectionConfig().setEnabled(http2Enabled)). This pins V1 to HTTP/1.1 and V2 to HTTP/2 regardless of the JVM-wide property, making the test deterministic in CI and locally. Verified locally: 29/29 tests pass with -DCOSMOS.HTTP2_ENABLED=true -DCOSMOS.THINCLIENT_ENABLED=true, which is the exact CI configuration that previously reproduced the failures. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

jeet1995 · 2026-06-04T13:24:44Z

/azp run java - cosmos - tests

jeet1995 · 2026-06-04T13:24:52Z

/azp run java - cosmos - spark

jeet1995 · 2026-06-04T13:25:02Z

/azp run java - cosmos - kafka

azure-pipelines · 2026-06-04T13:25:03Z

Azure Pipelines successfully started running 1 pipeline(s).

azure-pipelines · 2026-06-04T13:25:16Z

Azure Pipelines successfully started running 1 pipeline(s).

azure-pipelines · 2026-06-04T13:25:18Z

Azure Pipelines successfully started running 1 pipeline(s).

xinlian12

LGTM, thanks

github-actions Bot added the Cosmos label Apr 12, 2026

jeet1995 force-pushed the squad/48094-readconsistency-header-propagation branch from a3d4c0f to 26648a7 Compare April 16, 2026 00:36

jeet1995 changed the title ~~[Cosmos] Validate ReadConsistencyStrategy header propagation in thin client mode (#48094)~~ [Cosmos] Enable ReadConsistencyStrategy for Gateway V1 and thin client (Gateway V2) modes (#48094) Apr 16, 2026

jeet1995 changed the title ~~[Cosmos] Enable ReadConsistencyStrategy for Gateway V1 and thin client (Gateway V2) modes (#48094)~~ [Gateway V1/V2]: Enable ReadConsistencyStrategy. Apr 16, 2026

FabianMeiswinkel approved these changes Apr 16, 2026

View reviewed changes

jeet1995 and others added 12 commits April 21, 2026 17:18

Fix E2E tests for serverless accounts: remove throughput parameter (A…

3f80dac

…zure#48094) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Test: revert to 2022-08-15 with EnableNoSQLVectorSearch removed

8e262cb

Verifying that the API version rejection was caused by EnableNoSQLVectorSearch. This commit will be reverted after pipeline verification. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Test: re-verify 2022-08-15 + EnableNoSQLVectorSearch (expect 400)

7991337

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

jeet1995 force-pushed the squad/48094-readconsistency-header-propagation branch from 38a8292 to e00f5bb Compare April 21, 2026 21:18

jeet1995 force-pushed the squad/48094-readconsistency-header-propagation branch 2 times, most recently from d12a376 to f30f417 Compare April 21, 2026 23:01

jeet1995 force-pushed the squad/48094-readconsistency-header-propagation branch from f30f417 to ce56e3e Compare April 21, 2026 23:33

jeet1995 and others added 2 commits June 3, 2026 17:37

Cosmetic: drop redundant toString and relocate Logger field

3c0eacb

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Merge remote-tracking branch 'upstream/main' into squad/48094-readcon…

67499c7

…sistency-header-propagation # Conflicts: # sdk/cosmos/azure-cosmos-tests/src/test/java/com/azure/cosmos/implementation/RxGatewayStoreModelTest.java

FabianMeiswinkel approved these changes Jun 3, 2026

View reviewed changes

kushagraThapar approved these changes Jun 3, 2026

View reviewed changes

jeet1995 mentioned this pull request Jun 4, 2026

[cosmos] Add spy-wire test coverage for ReadConsistencyStrategy on Query, ChangeFeed, and readManyByPartitionKeys paths #49370

Closed

jeet1995 and others added 2 commits June 3, 2026 23:14

FabianMeiswinkel approved these changes Jun 4, 2026

View reviewed changes

jeet1995 enabled auto-merge (squash) June 4, 2026 17:16

xinlian12 approved these changes Jun 4, 2026

View reviewed changes

jeet1995 merged commit cec4b99 into Azure:main Jun 4, 2026
115 of 120 checks passed

Conversation

jeet1995 commented Apr 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Issue

Summary

Prioritization rules (the core of this PR)

What changed on the wire

Test coverage

End-to-end validation (Kusto)

.NET SDK reference

Proxy coordination

SDK Contribution checklist

Testing Guidelines

Uh oh!

FabianMeiswinkel left a comment

Choose a reason for hiding this comment

Uh oh!

jeet1995 commented Apr 16, 2026

Uh oh!

azure-pipelines Bot commented Apr 16, 2026

Uh oh!

jeet1995 commented Apr 16, 2026

Uh oh!

azure-pipelines Bot commented Apr 16, 2026

Uh oh!

jeet1995 commented Apr 16, 2026

Uh oh!

azure-pipelines Bot commented Apr 16, 2026

Uh oh!

jeet1995 commented Jun 3, 2026

Uh oh!

azure-pipelines Bot commented Jun 3, 2026

Uh oh!

jeet1995 commented Jun 3, 2026

Backend amplification re-verified (post-merge, fresh jar)

Kusto verification

Actual results — backend reads per (account, op, gateway path) cell

Client-side baseline (proves 15 client ops per cell)

Headline

Uh oh!

FabianMeiswinkel left a comment

Choose a reason for hiding this comment

Uh oh!

kushagraThapar left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

jeet1995 commented Jun 4, 2026

Uh oh!

azure-pipelines Bot commented Jun 4, 2026

Uh oh!

jeet1995 commented Jun 4, 2026

Uh oh!

jeet1995 commented Jun 4, 2026

Uh oh!

jeet1995 commented Jun 4, 2026

Uh oh!

azure-pipelines Bot commented Jun 4, 2026

Uh oh!

azure-pipelines Bot commented Jun 4, 2026

Uh oh!

azure-pipelines Bot commented Jun 4, 2026

Uh oh!

FabianMeiswinkel left a comment

Choose a reason for hiding this comment

Uh oh!

jeet1995 commented Jun 4, 2026

Uh oh!

jeet1995 commented Jun 4, 2026

Uh oh!

jeet1995 commented Jun 4, 2026

Uh oh!

azure-pipelines Bot commented Jun 4, 2026

Uh oh!

azure-pipelines Bot commented Jun 4, 2026

Uh oh!

azure-pipelines Bot commented Jun 4, 2026

jeet1995 commented Apr 12, 2026 •

edited

Loading

Actual results — backend reads per `(account, op, gateway path)` cell