[java-spanner] Provide a mutation count estimation and document how mutations are calculated
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
先從所要求的 MutationCountEstimator 範圍以及 Spanner 配額和提交統計資料文件開始，然後檢視連結的 google-cloud-go issue 1721。比較對 INSERT、UPDATE、INSERT_OR_UPDATE、REPLACE 和 DELETE 的要求涵蓋範圍，包括 STORING 和產生的欄位，以及索引的 write-only 階段。完成的要求是確定實作範圍或文件範圍，並制定驗證標準。
由索引模型根據 Issue 內容生成。
描述
Is your feature request related to a problem? Please describe.
The https://docs.cloud.google.com/spanner/quotas only describes how secondary indexes affect mutation counts for delete operations. For inserts and updates, the docs state that "operations count with the multiplicity of the number of columns they affect" but do not describe how secondary indexes contribute to the count.
The full formula for inserts (number of columns + sum of columns across all secondary indexes) was only confirmed informally by Google's backend team in https://github.com/googleapis/google-cloud-go/issues/1721.
Additionally, when creating a new index on an existing table, we observe an immediate increase in mutation counts for writes to that table during the schema change (write-only phase), before the index is fully backfilled. This behavior and its impact on mutation budgets is not documented.
This forces teams to reverse-engineer mutation counting logic, which is fragile and breaks when the internal counting rules change.
Describe the solution you'd like
- A utility class in the Java client (e.g. MutationCountEstimator) that can calculate the expected mutation count for a given set of mutations before committing
OR - Complete documentation of how mutations are actually calculated for all operation types (INSERT, UPDATE, INSERT_OR_UPDATE, REPLACE, DELETE),
including:
- Indexes with STORING clauses
- Computed/generated columns
- The impact on mutation counts during index creation (write-only phase before backfill completes)
Ideally both :D
Describe alternatives you've considered
- Reverse-engineering the count from schema metadata and secondary index definitions. This is error-prone and has caused production incidents when our
calculation diverged from Spanner's actual count. - Committing a single row first, reading getMutationCount() from CommitResponse, then using that to size remaining batches.
- Using a limit well below 80,000 (e.g. 75,000) to absorb miscalculations.
Additional context
- https://cloud.google.com/blog/products/databases/cloud-spanner-doubles-the-number-of-updates-per-transaction — references mutation counting but does not cover the index impact.
- https://github.com/googleapis/google-cloud-go/issues/1721 — open since 2019, requesting programmatic mutation calculation. The formula was confirmed informally but never made it into the docs.
- The https://docs.cloud.google.com/spanner/docs/commit-statistics provides post-commit mutation counts but not pre-commit estimation.
- 主要語言
- Java
- 星號
- 2.1k
- 分支
- 1.2k
- 平均合併
- 2 天 14 小時
- 30 天內合併 PR
- 192
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
googleapis/google-cloud-java 的其他 Issue
-
[java-core] Timestamp.of(java.sql.Timestamp) is one second late for a time less than a second before the epoch可能已有人在做 @Vcode2407 於 4 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 78/100
googleapis/google-cloud-java#14636 ·
維護者通常 1 天內回覆
-
[java-firestore] UserDataConverter encodes a pre-epoch Date with negative nanos, so the write is refused可能已有人在做 @wu-hui 於 23 天前認領。 未關閉priority: p2 type: bug
難度 2/5 1-3 小時 新手友好度 75/100
googleapis/google-cloud-java#14635 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
[java-firestore] UserDataConverter throws IndexOutOfBoundsException on an empty __binary__ value可能已有人在做 @wu-hui 於 23 天前認領。 未關閉priority: p2 type: bug
難度 2/5 1-3 小時 新手友好度 74/100
googleapis/google-cloud-java#14634 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
[java-firestore] CustomClassMapper.convertBigDecimal calls .abs() on Double, unintentionally flipping negative values to positive可能重新可做 @wu-hui 於 45 天前認領，目前沒有進行中的 PR。 未關閉
難度 2/5 1-3 小時 新手友好度 85/100
googleapis/google-cloud-java#14533 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Github CI failing when trying to install xmllint可能已有人在做 @blakeli0 於 81 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 65/100
googleapis/google-cloud-java#14132 · 1 則留言 ·
維護者通常 1 天內回覆
查看 googleapis/google-cloud-java 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
FasterXML/jackson-databind#6443 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 80/100
finos/fluxnova-bpm-platform#387 ·
維護者通常 4 天內回覆
-
難度 1/5 1 小時以內 新手友好度 88/100
-
難度 2/5 1 小時以內 新手友好度 84/100
cpp-best-practices/project_validator#251 ·
維護者通常 1 天內回覆