PyPI - mainsequence-metatable - Versions diffs - 0.1.28.dev49__tar.gz → 0.1.28.dev51__tar.gz - Mend

@@ -178,3 +178,7 @@ for restart recovery. On an uncertain outcome, inspect `upload_receipt()` before
 resubmitting; do not assign a fresh key to bypass uncertainty. Administrator
 reconciliation requires verified physical evidence. This workflow uses the Main
 Sequence API and has no Artifact or temporary-URL dependency.
+A 429 `transfer_capacity_exceeded` or 503 `database_connections_busy` means the
+API was at capacity and nothing ran. Retry after `Retry-After`, including SQL and
+writes; it is not an uncertain outcome.

@@ -240,6 +240,10 @@ Read `docs/operations/recovery-and-observability.md`.
 - Inspect partial DDL before retrying, especially on engines without transactional
   DDL. A finalization-only failure can be retried without reapplying committed
   revisions. Client DDL has no API executor journal.
+- Finalization sends at most 10 tables per request, the version table first, and
+  reports `Finalizing MetaTables 11-20 of 62.` for larger providers (client 0.1.28
+  and later). A run that stops partway leaves earlier batches active; rerun the
+  same upgrade to finalize the rest.
 - Destructive catalog deletion is not migration recovery and never bypasses
   schema-management protection.

@@ -124,3 +124,7 @@ for restart recovery. On an uncertain outcome, inspect `upload_receipt()` before
 resubmitting; do not assign a fresh key to bypass uncertainty. Administrator
 reconciliation requires verified physical evidence. This workflow uses the Main
 Sequence API and has no Artifact or temporary-URL dependency.
+A 429 `transfer_capacity_exceeded` or 503 `database_connections_busy` means the
+API was at capacity and nothing ran. Retry after `Retry-After`, an upload with the
+same operation UUID; it is not an uncertain outcome.

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence-metatable
-Version: 0.1.28.dev49
+Version: 0.1.28.dev51
 Summary: Main Sequence MetaTables Python client and standalone API
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: MIT

@@ -51,6 +51,10 @@
 > are when grants changed outside MetaTables are repaired, not on every catalog
 > change. MySQL and SQL Server keep the full sweep on every change.
+> Amendment (2026-10-09): [ADR 0022](0022-concurrent-requests-and-connection-reuse.md)
+> reuses login-role connections within a pod, only by the login role that opened them
+> and never through `SET ROLE`; no session state carries over from one use to the next.
 Date: 2026-09-29

@@ -1,9 +1,10 @@
 # ADR 0022: Concurrent requests per pod and reused database connections
-Status: Proposed.
+Status: Accepted.
-Implementation status: implemented on development; not deployed. Unit tests pass;
-the container suite and the load test against the development deployment are pending.
+Implementation status: implemented on development. Unit tests pass; deployment
+verification, the MySQL and SQL Server container suites and the load test against the
+development deployment are pending.
 Owner: this repository.

@@ -39,7 +39,7 @@ decisions belong in the SDK repository and are linked as dependencies.
 | [0016: Impact pre-flight for cascades and deletes](api/0016-impact-preflight.md) | Accepted; implemented; container engine verification pending | `get_impact` returns what a row delete, key update or table drop reaches, every blocker and whether the caller may write each table, from the planner the confirmed delete runs; cascade effects never block. Projects render it in their own UIs. |
 | [0017: Hosted caller identity through the SDK request identity](api/0017-hosted-request-identity.md) | Accepted; implemented for 0.1.21; hosted rollout verification pending | The hosted API installs the SDK request identity that the platform launcher requires; the SDK verifies each caller assertion once and admission reads `User.get_logged_user()`, including the caller's signed Teams and admin flag. Local keeps its loopback token admission. |
 | [0018: Table search by meaning and columns](api/0018-table-search.md) | Accepted; implemented; container engine verification pending | One route ranks visible tables by BM25 keywords and a local English embedding model over a per-table document that includes columns, merges the rankings and returns `matched_columns`; the index refreshes on every metadata write. |
-| [0022: Concurrent requests per pod and reused database connections](api/0022-concurrent-requests-and-connection-reuse.md) | Proposed; implemented on development; not deployed; container and load verification pending | One number per pod sizes its threads, data-request admission, catalog pool and login-role connections; connections are reused only by the role that opened them, and maximum pods × 3T stays within the database's connection limit. |
+| [0022: Concurrent requests per pod and reused database connections](api/0022-concurrent-requests-and-connection-reuse.md) | Accepted; implemented on development; deployment and load verification pending | One number per pod sizes its threads, data-request admission, catalog pool and login-role connections; connections are reused only by the role that opened them, and maximum pods × 3T stays within the database's connection limit. |
 ## Agents

@@ -73,7 +73,7 @@ DataSource and bootstrap state and returns `Cache-Control: no-store`.
 | 404 | Resource missing or not visible to the current actor. |
 | 409 | Lifecycle, capability, protection, reference, or physical-state conflict. |
 | 422 | Request/schema validation failure. |
-| 503 | Catalog, SDK verification/source access, physical connection, or an uncertain operation outcome is unavailable. |
+| 503 | Catalog, SDK verification/source access, physical connection, or an uncertain operation outcome is unavailable; or every database connection the API may hold stayed busy (`database_connections_busy`, `Retry-After: 1`). |
 Most framework errors use a `detail` field. Some domain operations provide a
 structured code and field information. Raw-query validation errors can be returned
@@ -87,4 +87,4 @@ An unknown physical commit outcome requires reconciliation, not a blind retry.
 ## Transfer errors
-Data routes return 413 for request/row/response byte limits, 408 for the overall transfer deadline, and 429 with `Retry-After: 1` when per-process admission capacity is exhausted. Existing SQL/driver errors can retain their engine-specific deadline codes and status. Upload conflicts use 409 and uncertainty can use 503. A limit enforced by schema validation can return 422. See [typed client exceptions and recovery](../client/bounded-transfers.md).
+Data routes return 413 for request/row/response byte limits, 408 for the overall transfer deadline, and 429 `transfer_capacity_exceeded` with `Retry-After: 1` when no data-request slot freed up within the request deadline (each API process runs `serving.concurrency` data requests at once). A 503 `database_connections_busy` with `Retry-After: 1` means every database connection stayed busy until the deadline. In both cases no statement ran, so any request, including SQL and writes, is safe to retry. Existing SQL/driver errors can retain their engine-specific deadline codes and status. Upload conflicts use 409 and uncertainty can use 503. A limit enforced by schema validation can return 422. See [typed client exceptions and recovery](../client/bounded-transfers.md).

@@ -132,6 +132,11 @@ statistics refresh (even though it uses GET), and receipt reconciliation do not
 automatically replay after uncertain failures. SDK authentication and one
 credential refresh remain; SDK and HTTP adapter write retry loops are bypassed.
+Capacity answers are the exception: 429 `transfer_capacity_exceeded` and 503
+`database_connections_busy` mean the API was at capacity and no statement ran.
+Retry any request after `Retry-After`, including SQL and writes; the client does
+so automatically only for safe reads.
 Exceptions are available in `metatables.transfer`: `TransferLimitError`,
 `TransferDeadlineError`, `TransferRetryExhausted`, `TransferConflictError`, and
 `TransferOutcomeUnknown`. Deterministic authorization/validation errors retain

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "mainsequence-metatable"
-version = "0.1.28.dev49"
+version = "0.1.28.dev51"
 description = "Main Sequence MetaTables Python client and standalone API"
 readme = "README.md"
 requires-python = ">=3.13"

mainsequence-metatable 0.1.28.dev49__tar.gz → 0.1.28.dev51__tar.gz

mainsequence-metatable 0.1.28.dev49tar.gz → 0.1.28.dev51tar.gz