[BUG] Cosmos P2: ORDER BY continuation predicates incorrectly escape strings

オープン
  • 何か問題がありますか？
#51,134 コメント 0 件 リアクション 1 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
68/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
azure, java
領域
backend-api-design, databases

調査の方向性

Start in OrderByDocumentQueryExecutionContext.java:444-447 and inspect how ORDER BY continuation predicates escape string values. First trace the helper's callers and related tests, then run the focused Cosmos query tests. Done means quotes, backslashes, and control characters produce valid predicates and resumed results match uninterrupted queries.

索引モデルが issue の本文から書いたものです。

説明

Client Cosmos

Describe the bug
Alan Zimmer's November 6, 2026 audit of com.azure:azure-cosmos:4.84.0-beta.1 reports that Java regex replacement processing consumes the intended escape backslash when constructing ORDER BY continuation predicates. A stored value a"b becomes the malformed SQL literal "a"b" in a resumed query. Backslashes and control characters are also unhandled and can change comparison values. Reported priority: P2.

Exception or Stack Trace
No SDK/service stack trace supplied. The reported helper output contains a malformed SQL string literal.

To Reproduce
Construct an ORDER BY continuation predicate for a stored value containing a quote, such as a"b. Also cover backslashes and control characters. Compare uninterrupted and resumed query execution and verify that continuation predicates preserve the original comparison values.

Code Snippet
No complete executable snippet supplied. Reported location: OrderByDocumentQueryExecutionContext.java:444-447 in the audited source. The exact helper reportedly emitted "a"b" for input a"b in a standalone JDK probe.

Expected behavior
String comparison values are correctly serialized or parameterized in continuation predicates. Resumed queries are valid and return results equivalent to uninterrupted queries for quotes, backslashes, and control characters.

Screenshots
N/A.

Setup (please complete the following information):

  • OS: Not reported.
  • IDE: Not reported.
  • Library/Libraries: com.azure:azure-cosmos:4.84.0-beta.1.
  • Java version: JDK probe; exact version not supplied.
  • App Server/Environment: ORDER BY query continuation.
  • Frameworks: Not reported.

Dependency mismatch: Not indicated; dependency tree/logs were not supplied.

Additional context
Proposed fix from the audit: use proper JSON string serialization or SQL parameters instead of ad hoc regex escaping.

Regression coverage: compare uninterrupted and resumed queries with string values containing quotes, backslashes, and control characters; assert valid predicates and identical comparison values/results.

Evidence: Alan reproduced the exact helper's malformed output at the standalone JDK-helper level, not through live query execution. No live Cosmos calls or full SDK test suite were run, and no repository files were changed. This issue tracks validation and implementation of the proposed fix, not an already-applied fix.

Information Checklist

  • Bug Description Added
  • Repro Steps Added
  • Setup information Added
主要言語
Java
スター
2.6k
フォーク
2.2k
平均マージ
2日 2時間
マージ済み PR（30日）
257

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Azure/azure-sdk-for-java のほかの issue

Azure/azure-sdk-for-java の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。