diff --git a/AGENTS.md b/AGENTS.md index 3a42cbf8c..95d729c9d 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -5,8 +5,8 @@ This document provides AI agents with essential context for working on the Exten ## Project Overview **ExtendDB** is an open source DynamoDB-compatible runtime with pluggable storage, released under the Apache 2.0 -License. ExtendDB is a clean-room implementation of the DynamoDB wire protocol, written in Rust and initially developed -by AWS engineers. It is not a fork of DynamoDB and contains no DynamoDB source code. ExtendDB speaks the DynamoDB wire +License. ExtendDB is a clean-room implementation of the DynamoDB wire protocol, written in Rust and maintained +by AWS. It is not a fork of DynamoDB and contains no DynamoDB source code. ExtendDB speaks the DynamoDB wire protocol: any AWS SDK, CLI, or tool that works with DynamoDB works with ExtendDB, unchanged. - **Language:** Rust (edition 2024, MSRV 1.88+) diff --git a/README.md b/README.md index a9f61dfdf..73b438a72 100755 --- a/README.md +++ b/README.md @@ -1,9 +1,9 @@ # ExtendDB -> **ExtendDB is an independent open source project managed by Amazon Web Services. It is not Amazon DynamoDB and does -> not contain any DynamoDB source code.** "DynamoDB" is a trademark of Amazon.com, Inc. ExtendDB is a clean-room -> implementation that speaks the DynamoDB wire protocol. Behavioral differences from the real service are documented -> in [Differences from DynamoDB](docs/differences-from-dynamodb.md). +> **ExtendDB is an open source project maintained by AWS. It is not Amazon DynamoDB and does not contain any DynamoDB +> source code. It is not an AWS service.** "DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. ExtendDB is +> a clean-room implementation that speaks the DynamoDB wire protocol. Behavioral differences from the real service are +> documented in [Differences from DynamoDB](docs/differences-from-dynamodb.md). A DynamoDB-compatible API adapter, ExtendDB speaks the DynamoDB wire protocol — any AWS SDK, CLI, or tool that works with DynamoDB works with ExtendDB, unchanged. diff --git a/crates/bin/README.md b/crates/bin/README.md index e1e898e91..eafcf1fdc 100644 --- a/crates/bin/README.md +++ b/crates/bin/README.md @@ -1,9 +1,9 @@ # ExtendDB -> **ExtendDB is an independent open source project managed by Amazon Web Services. It is not Amazon DynamoDB and does -> not contain any DynamoDB source code.** "DynamoDB" is a trademark of Amazon.com, Inc. ExtendDB is a clean-room -> implementation that speaks the DynamoDB wire protocol. Behavioral differences from the real service are documented -> in [Differences from DynamoDB](https://github.com/ExtendDB/extenddb/blob/main/docs/differences-from-dynamodb.md). +> **ExtendDB is an open source project maintained by AWS. It is not Amazon DynamoDB and does not contain any DynamoDB +> source code. It is not an AWS service.** "DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. ExtendDB is +> a clean-room implementation that speaks the DynamoDB wire protocol. Behavioral differences from the real service are +> documented in [Differences from DynamoDB](https://github.com/ExtendDB/extenddb/blob/main/docs/differences-from-dynamodb.md). ExtendDB is a DynamoDB-compatible API server. Any AWS SDK, CLI or tool that works with DynamoDB works with ExtendDB. This crate builds the `extenddb` binary. diff --git a/crates/server/src/console/pages/docs_page.rs b/crates/server/src/console/pages/docs_page.rs index 2f19f77e4..bff6fdc5f 100755 --- a/crates/server/src/console/pages/docs_page.rs +++ b/crates/server/src/console/pages/docs_page.rs @@ -35,7 +35,7 @@ pub async fn docs_page(State(state): State>) -> Response { let mut content = String::with_capacity(4096); content.push_str(r#"

Documentation

-

extenddb is not Amazon DynamoDB. It is an independent, clean-room implementation that speaks the DynamoDB wire protocol. It is not affiliated with, endorsed by, or sponsored by Amazon Web Services. “DynamoDB” is a trademark of Amazon.com, Inc.

+

ExtendDB is not Amazon DynamoDB. It is a clean-room implementation that speaks the DynamoDB wire protocol. ExtendDB is an open source project maintained by AWS. It is not an AWS service. “DynamoDB” is a trademark of Amazon.com, Inc. or its affiliates.

"#); let categories = [ diff --git a/crates/storage-sqlite/README.md b/crates/storage-sqlite/README.md index 4af5fd353..e9c29daf5 100644 --- a/crates/storage-sqlite/README.md +++ b/crates/storage-sqlite/README.md @@ -62,8 +62,8 @@ built with that feature needs no path configured. ## Developer mode -A build-time profile that makes ExtendDB a drop-in replacement for DynamoDB -Local: plain HTTP on loopback, open authorization, and a seeded credential — with +A build-time profile that builds ExtendDB dev, a drop-in replacement for +DynamoDB Local: plain HTTP on loopback, open authorization, and a seeded credential — with real SigV4 verification still in force. It is enabled by the `dev-mode` feature and, by a compile-time guard, **can never be built with the Postgres backend**. diff --git a/devtools/approved-licenses.txt b/devtools/approved-licenses.txt index 7ed0957af..cca5691f0 100755 --- a/devtools/approved-licenses.txt +++ b/devtools/approved-licenses.txt @@ -3,7 +3,6 @@ # # Amazon pre-approved open source licenses (SPDX identifiers) -# Source: https://policy.a2z.com/docs/82475/publication#0ac159cb-89be-3e40-bc20-f67d4b2dbad0 # Last reviewed: 2026-04-20 # # Lines starting with # are comments. Blank lines are ignored. diff --git a/docker/dockerhub-overview-cassandra.md b/docker/dockerhub-overview-cassandra.md index 1908c5698..b99c463be 100644 --- a/docker/dockerhub-overview-cassandra.md +++ b/docker/dockerhub-overview-cassandra.md @@ -113,11 +113,11 @@ The same images and their signatures are mirrored by digest to ## Note -ExtendDB is an independent open source project managed by Amazon Web -Services. It is not Amazon DynamoDB and does not contain any DynamoDB source -code. "DynamoDB" is a trademark of Amazon.com, Inc. ExtendDB is a clean-room -implementation that speaks the DynamoDB wire protocol; behavioral differences -from the service are documented in +ExtendDB is an open source project maintained by AWS. It is not Amazon DynamoDB +and does not contain any DynamoDB source code. It is not an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. ExtendDB is a +clean-room implementation that speaks the DynamoDB wire protocol; behavioral +differences from the service are documented in [Differences from DynamoDB](https://github.com/ExtendDB/extenddb/blob/main/docs/differences-from-dynamodb.md). More at [extenddb.org](https://extenddb.org) and diff --git a/docker/dockerhub-overview-dev.md b/docker/dockerhub-overview-dev.md index 830424556..b54222ebf 100644 --- a/docker/dockerhub-overview-dev.md +++ b/docker/dockerhub-overview-dev.md @@ -57,6 +57,6 @@ The routine signer is `release-dev-image.yml`; the break-glass signer `sign-imag ## Note -ExtendDB is an independent open source project managed by Amazon Web Services. It is not Amazon DynamoDB and does not contain any DynamoDB source code. "DynamoDB" is a trademark of Amazon.com, Inc. ExtendDB is a clean-room implementation that speaks the DynamoDB wire protocol; behavioral differences from the service are documented in [Differences from DynamoDB](https://github.com/ExtendDB/extenddb/blob/main/docs/differences-from-dynamodb.md). +ExtendDB is an open source project maintained by AWS. It is not Amazon DynamoDB and does not contain any DynamoDB source code. It is not an AWS service. "DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. ExtendDB is a clean-room implementation that speaks the DynamoDB wire protocol; behavioral differences from the service are documented in [Differences from DynamoDB](https://github.com/ExtendDB/extenddb/blob/main/docs/differences-from-dynamodb.md). More at [extenddb.org](https://extenddb.org) and [github.com/ExtendDB/extenddb](https://github.com/ExtendDB/extenddb). Licensed under Apache-2.0. diff --git a/docker/dockerhub-overview-mongodb.md b/docker/dockerhub-overview-mongodb.md index 0002fd234..3238b20d3 100644 --- a/docker/dockerhub-overview-mongodb.md +++ b/docker/dockerhub-overview-mongodb.md @@ -106,11 +106,11 @@ images and their signatures are mirrored by digest to ## Note -ExtendDB is an independent open source project managed by Amazon Web -Services. It is not Amazon DynamoDB and does not contain any DynamoDB source -code. "DynamoDB" is a trademark of Amazon.com, Inc. ExtendDB is a clean-room -implementation that speaks the DynamoDB wire protocol; behavioral differences -from the service are documented in +ExtendDB is an open source project maintained by AWS. It is not Amazon DynamoDB +and does not contain any DynamoDB source code. It is not an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. ExtendDB is a +clean-room implementation that speaks the DynamoDB wire protocol; behavioral +differences from the service are documented in [Differences from DynamoDB](https://github.com/ExtendDB/extenddb/blob/main/docs/differences-from-dynamodb.md). More at [extenddb.org](https://extenddb.org) and diff --git a/docker/dockerhub-overview.md b/docker/dockerhub-overview.md index 28150546a..790f2e0d6 100644 --- a/docker/dockerhub-overview.md +++ b/docker/dockerhub-overview.md @@ -43,6 +43,6 @@ The signer identity separates tiers: routine backend releases are signed by `rel ## Note -ExtendDB is an independent open source project managed by Amazon Web Services. It is not Amazon DynamoDB and does not contain any DynamoDB source code. "DynamoDB" is a trademark of Amazon.com, Inc. ExtendDB is a clean-room implementation that speaks the DynamoDB wire protocol; behavioral differences from the service are documented in [Differences from DynamoDB](https://github.com/ExtendDB/extenddb/blob/main/docs/differences-from-dynamodb.md). +ExtendDB is an open source project maintained by AWS. It is not Amazon DynamoDB and does not contain any DynamoDB source code. It is not an AWS service. "DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. ExtendDB is a clean-room implementation that speaks the DynamoDB wire protocol; behavioral differences from the service are documented in [Differences from DynamoDB](https://github.com/ExtendDB/extenddb/blob/main/docs/differences-from-dynamodb.md). More at [extenddb.org](https://extenddb.org) and [github.com/ExtendDB/extenddb](https://github.com/ExtendDB/extenddb). Licensed under Apache-2.0. diff --git a/docs/NOTICE.md b/docs/NOTICE.md index 1617a6b5c..70c8bd566 100755 --- a/docs/NOTICE.md +++ b/docs/NOTICE.md @@ -3,9 +3,9 @@ ## Notice -**ExtendDB (extenddb) is not Amazon DynamoDB.** This software is an independent, clean-room implementation that provides a DynamoDB-compatible API. It does not contain, derive from, or link to any Amazon DynamoDB source code, libraries, or proprietary components. +**ExtendDB (extenddb) is not Amazon DynamoDB.** This software is a clean-room implementation that provides a DynamoDB-compatible API. It does not contain, derive from, or link to any Amazon DynamoDB source code, libraries, or proprietary components. -"DynamoDB", "Amazon DynamoDB", "AWS", and "Amazon Web Services" are trademarks of Amazon.com, Inc. or its affiliates. This project is not affiliated with, endorsed by, or sponsored by Amazon.com, Inc. or Amazon Web Services. +"DynamoDB", "Amazon DynamoDB", "AWS", and "Amazon Web Services" are trademarks of Amazon.com, Inc. or its affiliates. ExtendDB is an open source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. **No warranty.** This software is provided "as is" under the Apache License, Version 2.0, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and noninfringement. See [LICENSE](../LICENSE) for the full terms. diff --git a/docs/adr/0000-template.md b/docs/adr/0000-template.md index 66e824bd0..8974e2502 100644 --- a/docs/adr/0000-template.md +++ b/docs/adr/0000-template.md @@ -38,6 +38,6 @@ feedback, dependency constraints, security review. One bullet per reason. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0001-documentation-format.md b/docs/adr/0001-documentation-format.md index 760da6fbe..300e04fcf 100755 --- a/docs/adr/0001-documentation-format.md +++ b/docs/adr/0001-documentation-format.md @@ -33,6 +33,6 @@ Markdown for all documentation. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0002-sql-injection-defense.md b/docs/adr/0002-sql-injection-defense.md index 121a451bd..3133ebac9 100755 --- a/docs/adr/0002-sql-injection-defense.md +++ b/docs/adr/0002-sql-injection-defense.md @@ -75,6 +75,6 @@ This is **not** the same as raw string interpolation of user input. The validati Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0003-catalog-migration-mechanism.md b/docs/adr/0003-catalog-migration-mechanism.md index 91cf126b6..59583dbe3 100644 --- a/docs/adr/0003-catalog-migration-mechanism.md +++ b/docs/adr/0003-catalog-migration-mechanism.md @@ -153,6 +153,6 @@ be recreated and reloaded after `init`. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0004-vector-search-exact-scan.md b/docs/adr/0004-vector-search-exact-scan.md index cda78693b..e26d30056 100644 --- a/docs/adr/0004-vector-search-exact-scan.md +++ b/docs/adr/0004-vector-search-exact-scan.md @@ -135,3 +135,14 @@ now, and gated on a measured need rather than on anticipation. **Not measured.** Cold cache, concurrency beyond one core, and real embedding distributions. Cold reads can only be worse; the other two do not change the layout decision. + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0005-index-build-lifecycle-ownership.md b/docs/adr/0005-index-build-lifecycle-ownership.md index f8795eda9..110099ce1 100644 --- a/docs/adr/0005-index-build-lifecycle-ownership.md +++ b/docs/adr/0005-index-build-lifecycle-ownership.md @@ -135,6 +135,6 @@ lifecycle, which now means any backend logic that bypasses the shared module. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0006-pgvector-storage-and-scoring.md b/docs/adr/0006-pgvector-storage-and-scoring.md index fe0fd554e..938858fb4 100644 --- a/docs/adr/0006-pgvector-storage-and-scoring.md +++ b/docs/adr/0006-pgvector-storage-and-scoring.md @@ -110,11 +110,13 @@ operators, which costs a per-row unpack of every candidate and gives up any inde on the column. That trade is worse than the documented asymmetry for an input class no real embedding produces. +--- + ## License Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0010-cassandra-ttl-expiration-queue.md b/docs/adr/0010-cassandra-ttl-expiration-queue.md index 9e35d5c56..69d302f9b 100644 --- a/docs/adr/0010-cassandra-ttl-expiration-queue.md +++ b/docs/adr/0010-cassandra-ttl-expiration-queue.md @@ -164,3 +164,14 @@ Deliberately out of scope for this change, in rough priority order: * **TTL alongside asynchronously propagated GSIs**, per the table above. * **Version fence hardening.** The fence now uses the `version` column; remaining follow-up is retiring the `item_data` fallback once no unversioned rows can exist (requires a fleet-wide rewrite pass or an explicit migration), after which the canonical-JSON coupling disappears entirely. * **Recovery-path test coverage.** The transitions this change introduced — draining a retired generation, retiring a drained bucket registration, an expired worker claim — are reasoned about but not yet covered by tests. + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0011-cassandra-foreign-key-emulation.md b/docs/adr/0011-cassandra-foreign-key-emulation.md index e721b3f2c..a57dcaaf5 100644 --- a/docs/adr/0011-cassandra-foreign-key-emulation.md +++ b/docs/adr/0011-cassandra-foreign-key-emulation.md @@ -48,6 +48,6 @@ Application-layer pre-checks for all child entity creation operations. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0012-cassandra-transaction-atomicity-patterns.md b/docs/adr/0012-cassandra-transaction-atomicity-patterns.md index 96c2fd51a..e20dd763a 100644 --- a/docs/adr/0012-cassandra-transaction-atomicity-patterns.md +++ b/docs/adr/0012-cassandra-transaction-atomicity-patterns.md @@ -51,6 +51,6 @@ Check-then-batch pattern for operations requiring both duplicate detection and a Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0013-cassandra-keyspace-awareness.md b/docs/adr/0013-cassandra-keyspace-awareness.md index 9381c75d0..1ef078b00 100644 --- a/docs/adr/0013-cassandra-keyspace-awareness.md +++ b/docs/adr/0013-cassandra-keyspace-awareness.md @@ -59,6 +59,6 @@ Dynamic keyspace construction with JDBC-style connection strings. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0014-cassandra-upsert-semantics.md b/docs/adr/0014-cassandra-upsert-semantics.md index c7e55c9a7..965eb543e 100644 --- a/docs/adr/0014-cassandra-upsert-semantics.md +++ b/docs/adr/0014-cassandra-upsert-semantics.md @@ -54,6 +54,6 @@ Use natural INSERT behavior for operations requiring UPSERT semantics. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0015-cassandra-account-keyspace-provisioning.md b/docs/adr/0015-cassandra-account-keyspace-provisioning.md index 541a46dfc..ef9cbc165 100644 --- a/docs/adr/0015-cassandra-account-keyspace-provisioning.md +++ b/docs/adr/0015-cassandra-account-keyspace-provisioning.md @@ -65,6 +65,6 @@ Create account keyspace during account creation (`ManagementStore::create_accoun Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0016-cassandra-index-table-primary-key-structure.md b/docs/adr/0016-cassandra-index-table-primary-key-structure.md index c946e4fa6..4f4090706 100644 --- a/docs/adr/0016-cassandra-index-table-primary-key-structure.md +++ b/docs/adr/0016-cassandra-index-table-primary-key-structure.md @@ -67,6 +67,6 @@ Cassandra-optimized ordering: `PRIMARY KEY ((pk), sk_*, base_pk, base_sk_*)` Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0017-cassandra-transaction-implementation.md b/docs/adr/0017-cassandra-transaction-implementation.md index fc505b916..0db834bea 100644 --- a/docs/adr/0017-cassandra-transaction-implementation.md +++ b/docs/adr/0017-cassandra-transaction-implementation.md @@ -468,6 +468,6 @@ Estimated effort: **3-4 weeks** for complete implementation and testing. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0018-cassandra-stream-implementation.md b/docs/adr/0018-cassandra-stream-implementation.md index 1c427e0cf..64a54660c 100644 --- a/docs/adr/0018-cassandra-stream-implementation.md +++ b/docs/adr/0018-cassandra-stream-implementation.md @@ -465,3 +465,14 @@ This refactoring should be done **as part of the Cassandra streams implementatio - [DynamoDB Streams API Reference](https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Operations_Amazon_DynamoDB_Streams.html) - [PostgreSQL Reference Implementation](../../extenddb/crates/storage-postgres/src/stream_engine.rs) - [Hybrid Logical Clocks Paper](https://cse.buffalo.edu/tech-reports/2014-04.pdf) (Kulkarni et al.) + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0019-cassandra-logical-backup-restore.md b/docs/adr/0019-cassandra-logical-backup-restore.md index 29696813e..d4bf968ba 100644 --- a/docs/adr/0019-cassandra-logical-backup-restore.md +++ b/docs/adr/0019-cassandra-logical-backup-restore.md @@ -49,3 +49,14 @@ The first implementation restores base table schema and items, matching the Post * Backup and restore execute synchronously in the request task for parity with the current backends. A production-scale iteration should persist jobs and move payload copying, retries, and reconciliation into background workers. * Interrupted `CREATING`/`DELETING` operations need a future reconciliation worker for guaranteed orphan cleanup. * Restoring secondary-index and other table-adjacent configuration requires a future schema extension. + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0020-cassandra-occ-update-item.md b/docs/adr/0020-cassandra-occ-update-item.md index 3875f1903..97ab4c629 100644 --- a/docs/adr/0020-cassandra-occ-update-item.md +++ b/docs/adr/0020-cassandra-occ-update-item.md @@ -59,6 +59,6 @@ Version-based OCC via LWT (option 1). Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0021-cassandra-lwt-delete-atomicity-gap.md b/docs/adr/0021-cassandra-lwt-delete-atomicity-gap.md index fc43622b8..0bd937077 100644 --- a/docs/adr/0021-cassandra-lwt-delete-atomicity-gap.md +++ b/docs/adr/0021-cassandra-lwt-delete-atomicity-gap.md @@ -113,6 +113,6 @@ hangs, GC pauses of 4–11 seconds, `system.paxos` growing without bound). Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0022-trust-policy-deny-over-allow.md b/docs/adr/0022-trust-policy-deny-over-allow.md index 935a6fe23..f33ed0dad 100644 --- a/docs/adr/0022-trust-policy-deny-over-allow.md +++ b/docs/adr/0022-trust-policy-deny-over-allow.md @@ -169,6 +169,6 @@ implicitly denied. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0023-catalog-migrations.md b/docs/adr/0023-catalog-migrations.md index b83f1e3ac..953d4d443 100644 --- a/docs/adr/0023-catalog-migrations.md +++ b/docs/adr/0023-catalog-migrations.md @@ -423,6 +423,6 @@ that each backend implements, as follows. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0026-credential-crypto-on-aws-lc.md b/docs/adr/0026-credential-crypto-on-aws-lc.md index cf0f95fa5..75d6e9ef9 100644 --- a/docs/adr/0026-credential-crypto-on-aws-lc.md +++ b/docs/adr/0026-credential-crypto-on-aws-lc.md @@ -92,6 +92,6 @@ HMAC-SHA256 and signature compare use aws-lc-rs (Option 2). Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0027-cassandra-index-row-version-stamps.md b/docs/adr/0027-cassandra-index-row-version-stamps.md index 2be1192f7..52d93c134 100644 --- a/docs/adr/0027-cassandra-index-row-version-stamps.md +++ b/docs/adr/0027-cassandra-index-row-version-stamps.md @@ -205,11 +205,13 @@ the ledger's image. the worker path is exercised by the crate's direct integration tests, which hold the worker guard. +--- + ## License Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/0029-crates-io-packaging.md b/docs/adr/0029-crates-io-packaging.md index 4860386cd..e5c0acd07 100644 --- a/docs/adr/0029-crates-io-packaging.md +++ b/docs/adr/0029-crates-io-packaging.md @@ -139,6 +139,6 @@ binary crate, and a Cargo feature selects its backend. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/adr/README.md b/docs/adr/README.md index 372bf38f3..7febe92df 100644 --- a/docs/adr/README.md +++ b/docs/adr/README.md @@ -55,3 +55,14 @@ decision, write a new ADR. | [0026](0026-credential-crypto-on-aws-lc.md) | Credential cryptography uses AWS-LC through aws-lc-rs | Accepted | | [0027](0027-cassandra-index-row-version-stamps.md) | Cassandra: index rows carry the base-row version as their write timestamp | Accepted | | [0029](0029-crates-io-packaging.md) | The workspace crates go to crates.io together, at one version with exact pins | Accepted | + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/backlog.md b/docs/backlog.md index 81200f62a..845f55321 100755 --- a/docs/backlog.md +++ b/docs/backlog.md @@ -102,6 +102,6 @@ Refreshed: v0.0.118 (P115) Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/build-docs.py b/docs/build-docs.py index 41409e13e..37c11b6d3 100755 --- a/docs/build-docs.py +++ b/docs/build-docs.py @@ -255,9 +255,9 @@ def substitute_placeholders(text: str, variables: dict[str, str]) -> str:

License & Disclaimer

Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See the LICENSE file in the project root for the full text.

-

This software is provided “as is” without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. “DynamoDB” is a trademark -of Amazon.com, Inc.

+

This software is provided “as is” without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +“DynamoDB” is a trademark of Amazon.com, Inc. or its affiliates.

""" diff --git a/docs/cassandra-setup.md b/docs/cassandra-setup.md index 6b08f4ce7..2bd29b768 100644 --- a/docs/cassandra-setup.md +++ b/docs/cassandra-setup.md @@ -391,6 +391,6 @@ rationale are documented in the Cassandra ADRs (`docs/adr/0010`–`0021`). Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/design/01-requirements.md b/docs/design/01-requirements.md index 47f5e2f68..dd1358d9a 100755 --- a/docs/design/01-requirements.md +++ b/docs/design/01-requirements.md @@ -668,6 +668,6 @@ DynamoDB SDKs support optional endpoint discovery via the `DescribeEndpoints` op Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/design/02-high-level-design.md b/docs/design/02-high-level-design.md index 9ee5e0a68..92ecd9fc3 100755 --- a/docs/design/02-high-level-design.md +++ b/docs/design/02-high-level-design.md @@ -464,6 +464,6 @@ There is no in-memory locking (no `Mutex`, `RwLock`, or similar) on the data pat Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/design/03-component-core.md b/docs/design/03-component-core.md index 53182b513..55a717111 100755 --- a/docs/design/03-component-core.md +++ b/docs/design/03-component-core.md @@ -476,6 +476,6 @@ impl DynamoDbError { Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/design/04-component-storage.md b/docs/design/04-component-storage.md index 020a462c9..56fbfca10 100755 --- a/docs/design/04-component-storage.md +++ b/docs/design/04-component-storage.md @@ -1400,6 +1400,6 @@ backups). Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/design/05-component-auth-v3.md b/docs/design/05-component-auth-v3.md index f6150436f..b28af7e80 100755 --- a/docs/design/05-component-auth-v3.md +++ b/docs/design/05-component-auth-v3.md @@ -492,6 +492,6 @@ These must match real DynamoDB error format (HTTP status, error code, message st Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/design/05-component-auth.md b/docs/design/05-component-auth.md index 01ded144d..e15266a80 100755 --- a/docs/design/05-component-auth.md +++ b/docs/design/05-component-auth.md @@ -1611,6 +1611,6 @@ pub fn decrypt_secret(encrypted: &[u8], key_b64: &str, aad: &str) -> Result`, `--forget-store ` and `--forget-backup ` and plain sync's report of the rows of other stores, with three `BackupCatalog` methods on the four backends: `list_backup_rows_by_root(kind, root, status)` as the interfaces block had it; `rewrite_store(from_kind, from_root, keys, to)`, which rewrites only a row still of the old kind and root and not CREATING and counts the rows it rewrote, so a row another writer moved, or the CREATING row of a server still on the old root, is left rather than moved without its bytes (PostgreSQL in batches of 5,000 keys, each one `UPDATE` over `unnest` of its keys in a transaction the client commits, under `SET LOCAL lock_timeout` 3 s and `statement_timeout` 30 s with up to three attempts on a lock timeout, so the statement of a command killed while it waits on a row lock commits nothing once the claim is gone and the batches before it stay committed; one statement over every key does not fit a fixed bound, since over a catalog of 400,000 rows with 0006's indexes and 1,449-byte descriptions one over 200,000 keys took 16.4 and 16.9 s in plain SQL on PostgreSQL 16, where a batch of 5,000 took 0.23 to 0.29 s; SQLite one `BEGIN IMMEDIATE` transaction, every key or none; MongoDB `update_many` in chunks of 1,000 keys that also `$inc` `lock_seq`, a convention: the update and a transaction that writes the document are serialized (when the update commits after the transaction's snapshot and before its write, the transaction re-runs and reads the row as the update left it; when the transaction wrote first, the update waits for it and applies its filter to the committed document), and a registration keeps the store its server is configured with; Cassandra per key; the trait doc says what a client's death in the call leaves on each); and `summarize_store_roots()`, the rows per store (kind, root, id) and status, which the design did not have: `list_backup_rows_by_root` takes a root, and nothing listed the roots (PostgreSQL and SQLite one `GROUP BY`, MongoDB a `$group`, Cassandra the status table's partitions with their entries counted and not re-read, which the report of other stores then checks against the root's listing kept to each store's id, printing what no row of its status stands behind as status entries). On Cassandra `list_backup_rows_by_root` reads the entries of all five status partitions of the root whatever status it is asked for, dedupes them by (account, ARN), reads each row once and keeps it when its kind and root match (and its status, when one is asked for), so a row whose only entry is under an earlier status (a status change whose entry batch failed, which is logged and not sent again, or whose writer died between its row and its batch) is listed under its own status by the move, the forget options and the report of other stores. A partial rewrite (between PostgreSQL batches, between MongoDB chunks, between Cassandra keys, or between the move's slices) leaves rows under both roots; every step is idempotent and the command exits 1 naming what is left. On Cassandra `rewrite_store` writes the new root's status entry before the row's lightweight transaction (`IF store_kind = ? AND store_root = ? AND backup_status = `) and deletes the old entry after it, the one exception to the module doc's row-first rule: a stop after the new entry leaves only an entry every reader skips, where the row first would leave a moved row that no listing of the configured store returns; an unknown outcome is settled by a `LOCAL_SERIAL` read, which counts the row as this call's write only when it carries `to` whole (kind, root and store id; `to`'s root under another store id is another store, left and not counted), and `NotMatched` reads the row at `LOCAL_SERIAL` first, keeps the new entry when the row already names `to` (this call's write), writes the entry again under the row's own store when the row is now of `to`'s root under another store id with the status read (another move to that root), and otherwise removes the new entry; either way it tries again, up to three attempts. `start_backup_delete`'s and `set_backup_deleted`'s lightweight transactions carry the store kind and root they read, so a DeleteBackup of a server on the old root that read the row before the rewrite does not apply, reads the row again and moves its status entry under the root the row now names: the moved row is never left without its own entry. The report of other stores reads `summarize_store_roots` and names each CREATING and DELETING row through `list_backup_rows` of that store's exact identity (on Cassandra through `list_backup_rows_by_root` of its root, kept to the store's id); a store of the configured root under another id counts as another store, and its line names `--forget-backup ` as the way to remove such a row, since `--move-store` and `--forget-store` refuse the configured root (the line naming those two options is printed only when another root is listed); it is printed after every sync that listed the root to its end, skipped when the run stopped or the listing failed, and a failed read of it exits 1. So 4(g)'s "rows for another store are reported" now holds for every such row, where item 34 had it for the prefixes whose backup id such a row holds (section 4, PR 10). `--move-store` needs the configured store healthy, refuses the configured root and a root with no rows (printing the stores the catalog holds rows for; a root matches as stored, byte for byte), takes the maintenance claim on every backend, SQLite included under its serve lock, and waits over the configured store and every store id the catalog records for the old root (`maintenance::wait_for_quiet` takes a slice of identities), since a CreateBackup of a server still on the old root has its row there. Each row of the old root is checked against the configured store as the PR 10 contract says, read thus: a CREATING row goes through the reconciler's per-row resolution (`resolve_dead_creating_row`, split out of `resolve_dead_creating_rows` so both callers share one body) with the configured store's calls and `OnIncomplete::Leave`: it is written AVAILABLE when the copy holds its complete backup, and any other probe result stops the move with no status written (the takeover's generation is the one change), since a copy without the complete backup proves nothing about the old root's prefix (a copy's order is arbitrary) and a FAILED row would have the configured store's reconciler delete the copy and a server still on the old root the original; the way out is a reconciler on the old root (a server, or on SQLite plain sync, configured with it), which resolves the row there, or `--forget-backup`; the PR 10 contract's sentence is edited with this item; a DELETING row whose prefix there holds no verified manifest is finished with `finish_backup_delete` behind the fence, and stays DELETED when the move then stops; an AVAILABLE row is probed by `probe_manifest` (now `pub(super)`) and its manifest's size and item total must be the row's, so another backup under the same ARN is reported, not moved; the old root's rows and the configured root's are grouped by (account, backup id) before any row is checked, and every old-root row of a group of more than one (with a row of the configured root, or among the moved rows, which only Cassandra can hold) stops the move, so no such row gets a resolution or a finished deletion (on Cassandra two spellings of an ARN share one prefix), and the configured root's rows are read before anything changes, so a failed read stops the move with nothing changed. Every stopping row is named in one pass and none moves while any does; with none, `StoreFence::check_catalog` re-reads the identity file once before `rewrite_store` (a refusal records the store unhealthy, as the fence does everywhere), which the move calls in slices of 500 keys (`REWRITE_SLICE`), or one key per call on a backend that rewrites key by key (Cassandra, `BackupCatalog::rewrite_store_runs_key_by_key`), with a beat of the claim before each 500 keys and the signal and the claim's local state (`HeldClaim::lost`, no write) read before every call, so a move whose claim another holder took during the rewrite (on MongoDB and Cassandra, a command stopped past `stale_job_after_secs`, which reads its claim lost as it resumes since no beat confirmed it within two periods) writes nothing after the one call it had sent or was about to send (one key on Cassandra, one statement of up to 500 keys on MongoDB), and a signal stops it the same way, with the earlier calls' rows moved and the rest left under the old root; the old root is listed again and a row still there is reported with exit 1 (a key the old root no longer lists counts as moved only when its row, read by its ARN, 16 at a time, names the configured store, and a row that names no such store, removed by another writer during the move or moved to a third store, is reported as gone; a re-list that fails after a rewrite that counted every key takes every key as moved, and a failed read of a key's row takes that key and the rest as moved), and a plain sync of the configured root follows, in whose report of other stores a row of the old root (an insert that landed during that sync) is named and exits 1; a move that stops runs no sync. One `extenddb::audit` line is logged per row moved, resolved or finished (section 4, 5.2, PR 10). The removals of `--forget-store` and `--forget-backup` delete no object and read no store, so they run on a store in any state and with none configured (`kind = "disabled"`; a configured root the command cannot open, such as a filesystem directory that does not exist, stops it before the claim, and `kind = "disabled"` runs it), under the claim on every backend, with the wait over the configured store when its identity is known and otherwise every store id the catalog records for the configured root (and the root's ids for `--forget-store`; with no store the wait covers the RUNNING restores). They open the store writing nothing (described as a read leaves it, so no default root is created and no `validate` probe file written; the identity file read, never created; when it agrees with the rows, `check_configured_store_read_only` runs once and is recorded), and on SQLite the command's own pass over what the stopped server left runs without the store's check (`ReconcilerState::for_maintenance_holder_without_store_check`). Each status is removed with a method that exists, no fourth one: AVAILABLE by `forget_available_backup_row` with its in-use rule, DELETED and FAILED by `remove_backup_row`, CREATING by `remove_dead_creating_backup_row` on the catalog's clock, DELETING by `set_backup_deleted` then `remove_backup_row` (no duty meets the DELETED state between them, by the order of the listings: one that listed rows before the claim listed this one DELETING, and one that lists it DELETED did so after the claim was taken and reads the claim held); a removal that meets another status reads the row once more and applies that status's removal. `remove_backup_row` takes the store kind and root the caller read and removes only a row still of them (Cassandra's lightweight transaction `IF backup_status = ? AND store_kind = ? AND store_root = ?`, `NotMatched` answering `false`), so a tombstone duty of a server on the old root does not remove a row the move rewrote after the duty read it. A DELETING row of the configured store is the exception to "delete no object": after the wait for the duties (so a stop during the wait leaves the row DELETING and its objects untouched), the forget finishes its deletion, behind the fence (`finish_backup_delete`, the deletion its DeleteBackup asked for), which needs the store's check to have passed, and otherwise refuses the row; when the check failed on an identity mismatch that the row's own store id takes part in (`IdMismatch`, `MultipleRowIds`: the backup manual's copied identity file), the refusal says so and names the way out the manual gives, the same command with `[backup.store] kind = "disabled"`, whose generic DELETING path removes the row and keeps its bytes, then the move's sync, which adopts the backup again, and a DeleteBackup of it; on SQLite the command's own pass may finish it first, and the removal of its DELETED row says so; a DELETING row of another store keeps its bytes unless a server configured with that store finishes the deletion (its reconciler, under the claim, as the DeleteBackup asked), and a sync of that root after its return with the bytes adopts the backup again. While the configured root has no identity file and the catalog holds rows for it (`FileMissingWithRows`: an unmounted volume), every row of that root is refused, and so on SQLite is every row of the defaulted root found missing while the catalog holds rows for it (moved away, or a symbolic link to a volume that is gone: `configure_described` reads `read_store_ids` for the path and for each path met while every symbolic link along it is replaced by its target, component by component up to 40 links (a chain of links, a relative target, a directory link), each also with its longest existing ancestor canonicalized, and answers `NotConfigured::DefaultRootMissingWithRows`, which the command's header prints in place of "no server has run with this database file"), since a server's check rewrites a missing file at a root with no rows and reports the store healthy. Both wait for running jobs as `purge` does, refusing when one still runs at the wait's end; a CREATING or FAILED row whose heartbeat, written after the wait, is within the owner window, or that is of a store the wait does not cover, is left, as is an in-use row (whose text names `extenddb backup remove-target --account ` for a failed restore's target), and the command exits 1. `--forget-backup` repeats (in order, stopping at the first ARN not removed; an ARN that no row, under either spelling, and no in-catalog backup carries is printed as having nothing to remove and counts as done, so a command line can be run again after a stop; every ARN's form is checked before the claim is taken), takes the ARN as the row carries it and names a row under the other spelling without removing it, reports an earlier release's in-catalog backup as one (exit 1, nothing changed), and then, when a store is configured, runs the store's check once and prints it, naming the next ARN whose manifest is missing; that check writes nothing (`check_configured_store_read_only`: the identity read without the create and without `validate`, the id compared with the one the command opened the store with, the manifest probe), and is not run when the root had no identity file as the command opened it. That is the remedy for a restored catalog whose newest AVAILABLE backup was deleted after the catalog's backup, which item 34 left with "put the prefix back"; `--prune-missing` keeps refusing on `ManifestMissing`, the host-local detector, and plain sync's refusal there names `--forget-backup` with the ARN. After its removals `--forget-store` sweeps, under the claim, the root's status entries, each checked against its row at `LOCAL_SERIAL` (`remove_orphan_status_entries`, answering `StatusEntrySweep { removed, repaired }`): an entry whose row is gone or names another store is deleted (on Cassandra a deleter whose lightweight transaction lands before a rewrite of its row and whose entry batch lands after it leaves one under the old root), and one whose row is of the root under another status is written again under the row's status and the stale one deleted; it prints both counts, then the store ids the catalog still records for the root, without changing the exit (section 4, PR 10). The reconciler's `Duty::fenced` re-reads the row after the fence and skips one that is gone or whose status or store changed, then reads the maintenance claim again and starts nothing while it is held, two catalog reads per deletion; each FAILED-prefix and DELETED-prefix deletion and each tombstone removal that read the claim free must end by its deadline, `DUTY_DELETION_BOUND` (30 s, the S3 store's per-call bound, under the SDK's 60 s attempt timeout) after that read was sent: a read answered after the deadline starts nothing, the prefix deletion runs through the store's new `delete_prefix_before(prefix, deadline) -> PrefixDeletion { deleted, finished }` (the filesystem walk checks the deadline beside its cancel flag before each removal, the S3 loop before each `ListObjectsV2`, `DeleteObjects`, `ListMultipartUploads` and `AbortMultipartUpload`; the trait's default checks once, for a one-step store), and the call is also dropped at the deadline; past it the duty stops for the cycle, the row left for the next. Beside servers the forget options wait `FORGET_WAIT`, the bound plus one 30 s store call, from the claim before their first FAILED or DELETED removal and print the wait; on SQLite, under the serve lock, they do not wait. So what a deletion duty can still do to the bytes of a row a forget removes (4(a)) is the step in flight at its deadline, one removal on a filesystem root or one S3 request (up to 1,000 keys); the bound, like every lease in the design, assumes the server's process keeps running, and one paused past the wait between its last check and a call already sent (SIGSTOP, a frozen cgroup, a VM pause) runs that call when it resumes. A marker written per deletion, which the forget's removal would be conditioned on, is the full remedy, and is not taken: it adds a catalog write to every deletion for a case outside every other lease. The store-backed CreateBackup reads the claim again immediately before `claim_backup`, and the store-backed restore immediately before its registration as well as after it, so a claim taken before that read refuses the job with no row or record (`LimitExceededException`); what remains is the window from that read to the insert, however long the insert takes: a CreateBackup of a server still on the old root whose insert lands during the move's wait is listed by it, one that lands before the rewrite is left CREATING under the old root and reported by the re-list (the rewrite skips CREATING rows), one that lands during the move's sync of the configured root is named by that sync's closing report of other stores if it lands before it (exit 1), and one that lands after only by a later plain sync; the backup manual says to check plain sync's report of other stores before deleting the old root. `OTHER_STORE` now names the move ("or copy its tree under the configured root and move the backup's rows to the configured store with `extenddb backup sync --move-store `, and restore again"), as 5.3 step 7 says, and the reconciler's module doc with it. Each of the three confirms the maintenance claim with a beat of its own (`HeldClaim::recheck`, item 34) right before each step that cannot be undone, and stops when it finds the claim lost: the move before a dead CREATING row's resolution, a DELETING row's finished deletion and each 500 keys of the rewrite, reading the claim's local state before every other call of it (`MoveTarget::claim`); the forget options before each row's removal, a DELETING row's DELETED write or finished deletion and the removal of the DELETED row it leaves, and `--forget-store` before its sweep of the status entries (`ForgetRun::claim`). A stop there leaves the row as the steps before it left it, and the command's stop line names the step. As for sync and purge, what remains is a stop after the re-check confirmed the claim and before the step's own call reached the catalog or the store, or with that call already sent: the call lands when the process resumes, though on MongoDB and Cassandra another command may have taken the claim over during the stop. The three options conflict with each other, with `--adopt-store` and with `--prune-missing`. Memory: every backend reads a listing's rows whole, and the move makes two such reads, the old root's rows, which it keeps without their parsed description, and the configured root's rows, of which it keeps the (account, backup id) pairs for the two-rows check (its sync reads them again); after the rewrite it reads each moved row by its ARN rather than listing the configured store. Each read is about 27 KiB per row on SQLite and 23 on PostgreSQL above about 50 MiB, at 1,452 bytes of table description per row and growing with it: a move of 20,000 rows of a five-GSI table into an empty store peaked at 569 MiB on a SQLite debug build and 500 MiB on a PostgreSQL one, and a move of 50 rows on the PostgreSQL debug build at 49 MiB into an empty store and 231 MiB into a store of 8,000 rows (section 7). The PR 10 section's split line, interfaces block and sync contract, and section 7, are edited with this item; 4(c), 4(f), 4(g), 5.3 step 7, PR 8's claim-held paragraph and the PR 10 acceptance and transition lines state what was built and stay as written. The backup manual's procedure copies the old tree without its `extenddb-store.json` (the restarted servers gave the new root its own; a copied file turns every running server's store unhealthy until a restart, and, when a backup was taken under the new root meanwhile, needs that backup's row forgotten before the move, whose sync adopts it again). Not in #820: `migrate-legacy` (#821), a sweep of Cassandra's orphan status entries beyond `--forget-store`'s root, the same all-partition read for Cassandra's store-scoped `list_backup_rows`, which the reconciler reads (a DELETING row of the configured store whose entry batch failed is not finished by its reconciler until the entry is repaired; `--forget-backup` of its ARN finishes and removes it), and any detection of a server left configured with the old root, which the backup manual's procedure reconfigures first. 37. (2026-11-06, PR 10c as implemented, #821.) #821 ships `extenddb backup migrate-legacy |--all` (exactly one, a clap group; `` is checked as a backup ARN by clap, exit 2, before anything is opened) on the four backends, written in the engine's `backup/migrate_legacy.rs` against `BackupCatalog + LegacyBackupReader` and the configured store, so it runs on `Fake` and `MemStore`. The format gains `SnapshotDescriptor::KIND_LEGACY_IN_CATALOG` (`legacy_in_catalog`, the marker empty) with no format version change and no fixture byte changed; for that kind `source_backend` and `source_extenddb_version` name the binary that wrote the copy, since the in-catalog creator's version was never recorded. The manifest's `source_table` is, by one rule on every backend, the table the legacy restore creates (`source_table_from_legacy`, beside `restore_input`, pinned by an exhaustive property against `restore_input` and `restore_input_from_manifest` over the definition shapes): `restore_input` with no overrides (a backup with no definition keeps its keys and its key attribute definitions), with the table's and each GSI's throughput as the backup recorded them (none on demand; a provisioned GSI that recorded none or 0/0 keeps that, as CreateBackup records it from DescribeTable; a backup with no definition and no recorded throughput records none), so DescribeBackup reports the same throughput before and after the migration and a restore of the copy gives such a GSI the table's throughput and such a table the legacy 5/5 (`restore_input_from_manifest` reads a provisioned `source_table` with no throughput as 5/5, which only such a copy has), plus the definition's table class, TTL and stream and the SSE description built from the specification in the server's region (the region the legacy DescribeBackup names it in); the vector state is `[]` on PostgreSQL and SQLite with no names recorded (PostgreSQL with no definition and a NULL or zero snapshot too), `null` on MongoDB and Cassandra, and refused for a SQLite backup with no definition. So the stored specification loses its own `KMSMasterKeyId` in the copy; no answer of the server reports a key id before or after the migration (every backend's SSE description names `key/default`), so nothing a client reads changes (item 33's general difference). `LegacyBackupReader` gains seven members (section 3): `items(account, arn)`, the backup's name, recorded source, vector state and a `'static` item stream, each a frozen copy of its restore's read (PostgreSQL a `REPEATABLE READ READ ONLY` catalog transaction whose first statement re-checks AVAILABLE, owned by a spawned task that sends through a one-slot channel, held for the backup's whole copy as the restore holds it; SQLite the restore's keyset batches, each in its own read transaction re-checking AVAILABLE; MongoDB a cursor on `_backup_` with `batch_size` `DEFAULT_FETCH_BATCH` and a frozen copy of `document_to_item`, `Unsupported` for a document with no `backup_id`; Cassandra the buckets in order, paged by `item_index` 8 rows at a time, `LEGACY_ITEMS_PAGE`, where the restore's copy reads a whole bucket of 64, each page at consistency `ALL`, since the in-catalog create wrote each row at `ONE` and a read of fewer replicas can end short; a replica that does not answer, unavailable, timed out or failed, fails the backup naming it, "a replica of the account keyspace did not answer; run again when every replica is up"); `list_all()`, the in-catalog backups of every account that are not DELETED, by creation time then ARN (Cassandra a range read filtered to `store_kind` null), and `list_deleted()`, the DELETED ones, both returning a row that does not decode as an error; `holder_status(account, arn)`, the status, DELETED included, of an in-catalog backup at the ARN that the replacement did not replace (PostgreSQL and SQLite the `backups` row, MongoDB a document without the `migrated_to_store` marker, Cassandra a row with `store_kind` null); `finish_replacement(account, arn)`, which on MongoDB finishes a replacement that committed and stopped before its drop and answers `false` elsewhere; `remove_deleted(account, arn)`, conditioned on a DELETED in-catalog backup that is not a replacement's (PostgreSQL and SQLite the `backups` row, MongoDB the document without the marker, Cassandra the `backups_by_arn` row by a lightweight transaction `IF backup_status = 'DELETED' AND store_kind = null`, a lost answer settled by a read); and `replace_with_index_row(row) -> Replaced { Replaced, AlreadyReplaced, NotAvailable(String), InUse(String), NotApplied(String) }`, `NotApplied` being Cassandra's conversion whose condition failed at every attempt, which wrote nothing. `BackupCatalog` gains `row_holding_backup_id(backup_id)`, the row of the id whatever its account, ARN, table and store: the id alone is unique in the index (`idx_backup_index_backup_id` on PostgreSQL and SQLite, the unique `backup_id` index on MongoDB), so the inserts conflict on it, another account's row included (PostgreSQL, SQLite and MongoDB read by the id; Cassandra, which indexes no backup id, answers none). The replacement takes the place of the PR 10 paragraph's "insert the row and delete the legacy rows through the reader's `delete`": DeleteBackup does not read the maintenance claim, so in that order a DeleteBackup between the AVAILABLE check and the insert was answered DELETED for a backup that then came back as the migrated row, a restore target in CREATING made the `delete` refuse after the insert and ListBackups list the backup twice, and on Cassandra, where the legacy row and the index row share the `backups_by_arn` key, the frozen `delete` would remove the migrated row's list rows and leave a DELETED row that every later insert answers `false` for. Per backend: PostgreSQL one catalog transaction (the `backups` row `FOR UPDATE`, the CREATING-target check, the insert statement of `insert_backup_row` factored out, then the items, the definition and the `backups` row deleted); SQLite the same under the write lock and `BEGIN IMMEDIATE`; MongoDB one session transaction (`$inc lock_seq` while AVAILABLE, the CREATING-target check, the upsert, DELETING with `migrated_to_store: true`) and then the frozen drop of the collection and DELETED, a commit whose answer is lost being settled by reading the marked document and the index document back (the call's own replacement answers `Replaced`); Cassandra the row converted in place by one lightweight transaction `IF backup_status = 'AVAILABLE' AND store_kind = null AND active_restores = null` (after `creating_restore_target`, which clears stale registrations), then the index entries (`write_index_entries`, sent once more on a failure) and the buckets deleted; an unknown outcome is settled by a serial read of the index row, and `NotMatched` is read again, up to three attempts, and answered from what it finds. An index row of the account, ARN and store is `AlreadyReplaced` (what is left of an AVAILABLE in-catalog backup, on MongoDB of a DELETING one too, is removed; a DELETED or missing one is left); on Cassandra, finishing a conversion that stopped after its transaction writes the entries only when the serial read finds the index row AVAILABLE, and otherwise deletes the buckets and answers `NotAvailable`. One of the id under another ARN or store is `AlreadyExists` with nothing written, whatever the in-catalog backup's status (a DELETED one included, so the caller keeps a copy that may be that row's prefix); Cassandra reads only the ARN's partition and finds no row of the id under another spelling there, which the engine covers by reading the row of the id whatever its ARN (`row_holding_backup_id`) and, where that finds none, the manifest under the prefix. The row is written unowned (`owner_generation` 0) with `completed_at` and `heartbeat_at` on the database's clock, as `insert_backup_row` writes one (4(e)). Four frozen paths change, each to order a request wholly before or after a replacement: PostgreSQL's legacy `delete` reads the status under its row lock and answers not found for anything but AVAILABLE (so of two concurrent DeleteBackups of one in-catalog backup the second now answers BackupNotFound, where it answered DELETED); MongoDB's reads a DELETING document marked `migrated_to_store` as not found, in `delete` and in the lock's miss; Cassandra's DELETING claim carries `AND store_kind = null`, and so does Cassandra's legacy restore registration, whose `false` re-reads the row and answers not found for an index row (a legacy restore that read the backup before a conversion and registered after it had registered on the index row, answered CREATING and then lost its target). SQLite's are unchanged: the command holds the serve lock. A frozen `delete` leaves a DELETED in-catalog row with no items, definition or collection; the replacement leaves no in-catalog row on PostgreSQL and SQLite, a DELETED document with the marker on MongoDB, and on Cassandra no in-catalog row and no buckets. So a DELETED in-catalog row with no marker is always a DeleteBackup's, PR 14's refusal counts the rows that are not DELETED (a migrated backup leaves no in-catalog row on PostgreSQL and SQLite) and the DELETED ones whose id has the 14-digit shape, which `--all` removes once their prefixes are clean (below), and on Cassandra a migrated row carries `store_kind` and is kept (PR 14). The command takes the maintenance claim on every backend, SQLite included under the serve lock, for its whole run (4(f)), through one `take_claim` that `purge`, `sync` and this command share, and waits as `purge` does over the configured store's identity, after `resolve_dead_owners` and with a zero window on SQLite (the PR 10 contract's SQLite rule; those resolutions remove a legacy backup left CREATING, a dead create, and now log each removal under `extenddb::audit`); it needs the configured store healthy and its identity known. The backup job's writer runs under a `ClaimWatch` (`confirms_the_claim`, the loss token, the reason), the job's `HeartbeatHandle` or the maintenance claim's `HeldClaim`, whose timer cancels a `lost_signal` token when it records the loss, so a loss stops the copy at the writer's next await; the job's tests run unchanged. `HeldClaim` confirms the claim by the job's rule (`job/heartbeat.rs`, item 32), as item 34 gave it, with one restriction this item adds: each beat is bounded by one period (`MaintenanceClaim::heartbeat_within`, whose SQLite bound starts once the beat holds the write lock), a beat that answers `Lost`, fails or outlives the bound records the loss, and `lost()` also answers once the last confirmed beat (dated when its answer arrived) is older than two periods, unless the claim's beat parks before its bound (`heartbeat_parks_before_its_bound`, SQLite) and a beat on schedule is in flight. On PostgreSQL, MongoDB and Cassandra a beat in flight confirms nothing, as in the job's rule. The restriction: a parked beat confirms only while on schedule, having started within one period of the last confirmed beat (and a tenth of one for the timer's lateness; the beats fall one period apart from the take), since a process stopped and resumed starts its next beat late. The timer marks its flight with a drop guard, so a timer that ends mid-beat clears it, and records a confirmation before the flight ends. A heartbeat that hung kept the claim "confirmed" to the writer and to the check before the replacement while the stale window let a second command take the claim over and act on the same prefix. That reading is passive, and the job's other fences (generation-conditioned writes, a prefix of its own) have no counterpart here: before each step that cannot be undone (the manifest's put, every deletion under a store prefix, each replacement call and `finish_replacement`, a deleted backup's record removed) the command calls `HeldClaim::recheck()`, one beat under the period's bound that it waits for (a confirmation counts as a beat; a failure records the loss), and a failure stops the run with what it wrote left, saying so. PostgreSQL's maintenance take now refuses while the `backup_maintenance` row's heartbeat is younger than `stale_job_after_secs`, even with the advisory lock free, as the other backends' take does: a holder whose catalog session ended (a catalog restart or failover, `pg_terminate_backend`, a reset of that connection) runs until its next beat finds the loss, and a second command that took the claim at once replaced the backup while the first put its manifest over the second's copy, failed its re-read and deleted the prefix, leaving an AVAILABLE row with an empty prefix. On PostgreSQL, MongoDB and Cassandra a holder then starts no store or catalog call more than two periods after the answer of its last confirmed beat, whose write of the record's heartbeat came no earlier than the beat's start, at most one period before that answer; a taker needs the heartbeat older than the stale window, at least three periods, so a holder starts nothing once a take can succeed (the margin is the window less three periods, 255 s at the default and zero at the floor). On SQLite the serve lock keeps every other process out. A call already sent when the process stopped completes on resume, which the copy's writes and deletions are made safe against (below). After a killed command on PostgreSQL the next one fails at once, naming the holder, until the window passes, a breaking change for an operator who reruns a killed command at once; the PostgreSQL claim cell of a dead holder asserts that refusal before it ages the row's heartbeat, and no wire cell took a dead command's claim at once (the store and job wire suites pass unchanged on PostgreSQL). The change applies to every reader of `lost()`: `purge`'s deletion loop and the waits and loops of `backup sync`'s options stop on a stalled heartbeat too. `--all` reads `list_all`, then `list_deleted`; `` is resolved through `holder_status` under the ARN as written and rebuilt in this server's region, in the ARN's account, so it no longer reads every account's backups; with no in-catalog backup there, `finish_replacement` runs under both spellings ("finished" when it did), then a catalog row of the configured store is "already in the store" (exit 0) when AVAILABLE and "deleted" (exit 0) when DELETING or DELETED, after a replacement call with that row, which on Cassandra finishes a conversion that stopped after its lightweight transaction (`--all` does not list such a row, an index row; the backup manual says to finish it with ``, and to do so before deleting the backup, since a conversion stopped there and then deleted leaves its buckets until PR 14 drops `backup_items`); another row's store, or a CREATING or FAILED row, is refused. Per backup, in this order: the id (the 13-digit shape every 0.1.x backup has, refused before anything is read); the table name by the store-prefix rules and the partition; a DELETING backup handed to `finish_replacement` first, so MongoDB's marked document is finished whatever its index row holds, and reported by the row ("finished" while it is AVAILABLE, "deleted" when there is none or a DeleteBackup moved it on); a catalog row of the id under either spelling (`read_catalog_row`, as DescribeBackup reads it) and then under any ARN (`row_holding_backup_id`), where one of the configured store under the stored spelling is finished and reported by its status (AVAILABLE "finished", DELETING or DELETED "deleted", other refused without the call) and any other is refused before anything is deleted, since the prefix carries no region and may be that row's; the status (CREATING and DELETING skipped, named); the open (`Unsupported` refused, "the legacy restore cannot read it either"); the name (`is_valid_backup_name`, now exported from core); what `ensure_restorable` refuses ("the legacy restore refuses it too"); the unknown vector state. Then the copy: objects under the prefix with no row of the id are an earlier run's when the manifest there, if any, names this backup (one that names another, or does not read, refuses the backup with the prefix left: on Cassandra this is what tells another row's prefix), and are deleted through the deletion fence first, always rewritten, one rule, by the prefix walk, which starts no removal at or after `HeldClaim::acting_deadline()` (two periods after the last confirmed beat; a pass that reaches it is followed by a beat and another pass) and is dropped, its walk stopped at the next removal, when the timer records a loss; the fence also runs before the first put (a refusal stops the run, 4(c)) and before each deletion of a copy (a refusal is a note). Every object of a copy is written with `put_if_absent` (the writer's `Pipeline::written` records each object stored; a backup job keeps `put`, its prefix being its own), and an object already under a key stops the run with that object left (`Stop::Occupied`, "writes and deletes nothing more"). A run deletes its own copy object by object, the last written first, with `BackupStore::delete_written`, which the store trait gains: S3 `DeleteObject` with `If-Match` on the put's `ETag` (a 412 leaves the object), a filesystem root renaming the file to a hidden temporary name, removing it if its size and modification time are the put's and linking it back otherwise, and for a test double an unconditional delete; `lost()` is read before each object. A run stopped inside a store call past the stale window (SIGSTOP, a paused VM) completes that call on resume: such a put cannot replace another run's object (it may add one, which stops that run at the key), and such a deletion reaches another run's object at its key only on S3 when the two have the same bytes, or on a filesystem root when the process stops again between the rename and the link back (the other file is left under a hidden name); a walk completes its step under way. With `put` and `delete_prefix`, a first run stopped at the rename of a data file, or at its walk's first removal, and resumed after a second run had migrated the backup replaced or removed a file of the second run's AVAILABLE copy. Item order `unordered`. The count is checked twice, the items written against the in-catalog count after the data files and the manifest's total against it after the re-read through `verify_prefix` (the sidecar, the digest, `from_json_bytes`, every data file at its listed size: sync's check, 4(g)); the manifest's `source_table.item_count` is the recorded count and `table_size_bytes` the sum of the copied items' sizes, so after a migration `BackupSizeBytes` is the store's bytes and the source table's size that sum, either of which can differ from the in-catalog backup's; the name, ARN, id, creation times and item count do not change, and neither does the rest of DescribeBackup's answer except `SourceTableFeatureDetails` for a source that recorded no index, stream, TTL or SSE (every backup taken before catalog 0.0.4 among them): the in-catalog answer omits the member, the row's is `{}`, as for a store-backed backup and on the service, since the manifest's `source_table` has no member to tell the two apart and adding one is a format version change. The manifest's put and the replacement are called only after the deletion fence (`check_catalog`) and the claim's re-check, either failing stopping the run with the copy and the in-catalog backup kept; an `AlreadyExists` answer (a row of the id written since the reads above) refuses the backup and leaves the copy. A read that failed or ended short is re-read through `holder_status`, and a backup no longer AVAILABLE is skipped, "deleted during the copy". A DELETED in-catalog backup (a DeleteBackup of the legacy ARN, which the claim does not hold back) is refused when a catalog row of its id exists: one under its own ARN and AVAILABLE means the deleted backup is in the catalog again (a `backup sync` of #825 or #880, which has no in-catalog skip, adopted a stopped run's copy), and the refusal names the row and the choice (DeleteBackup the ARN again, or keep it), in `--all` too and with no audit line; one under another ARN may own the prefix. Otherwise, behind the fence, a copy a stopped run left under its prefix is deleted (when its manifest, if any, names this backup), the store is listed again, and once it lists nothing the DELETED in-catalog row is removed (`remove_deleted`), each after the claim's re-check; the backup is reported "deleted", with a note for each (`--all` names no deleted backup it did nothing for; an id of the 13-digit shape is never listed in the store nor removed). So `list_deleted` shrinks, and a DELETED in-catalog row whose id has the 14-digit shape is a prefix not yet confirmed clean. A backup DeleteBackup answered DELETED after a run stopped with its copy written (a kill after the manifest, a lost claim, a replacement whose answer did not come, a copy whose deletion the store refused) does not come back while that row is there: sync skips its prefix (below) and the next `--all` deletes the copy and then the row. PR 14's migration refuses while such a row exists (its lines), so the guarantee outlives the reader once `--all` has run after the last DeleteBackup of an in-catalog backup. Outcomes: `migrated`, `finished`, already in the store, `deleted`, `refused` (reason and way out; `InUse` names `backup remove-target`), `skipped` (CREATING, DELETING, deleted, deleted during the copy, or no longer AVAILABLE at the replacement) and `failed` (a store call, a stream error, a copy that does not read back), a `refused` or `failed` line saying "Its in-catalog backup is kept" only where one is (not for a deleted backup, nor after a replacement call whose answer did not come, nor once the claim is lost), each counted apart in the summary; a refusal or failure after the first put deletes the copy through the fence. Exit 0 only when every backup reached is in the store or deleted and the run reached its end, so with `--all` a skipped backup makes it exit 1 (on Cassandra a create in flight does). Global stops, exit 1 with the claim released: the listing, a catalog call, a lost claim, a signal, the fence before a put, the writer's unhealthy store, and a replacement whose call fails (its outcome unknown: the copy is left, and the next run finishes it if the row landed, else deletes it and, while the backup is AVAILABLE, writes it again). A signal is acted on before each backup and, inside a copy, at the writer's next step through its shutdown token, the copy deleted and named in a note; a second signal exits at once with status 130, leaving what a kill leaves; once the manifest is written the replacement is not interrupted, and a signal received meanwhile stops the run after it, whether or not another backup follows. One `extenddb::audit` line per backup the run deleted or replaced anything for (a migration, a finish that removed an in-catalog backup, MongoDB's stopped replacement finished, a deleted backup's copy deleted or its row removed), whatever its outcome (a refused, skipped or failed backup whose earlier copy the run deleted; on Cassandra every finish, which writes the row's entries again), none for an outcome that wrote nothing (an ARN already in the store with nothing left, a deleted backup with nothing to do); the command's log lines go to standard output with its own. `backup sync` gains `SkipReason::InCatalog { backup_arn, status }`, not transient, from `holder_status` under both spellings before the row read under them: "an in-catalog backup (STATUS) holds this ARN; run extenddb backup migrate-legacy ", and for a DELETED one "an in-catalog backup with this ARN was deleted; this prefix is a copy a stopped migration left, which extenddb backup migrate-legacy deletes"; `sync` and `startup_sync` now need `LegacyBackupReader` (every caller's storage has it); on Cassandra it answers before the insert's `false`. That makes 4(g)'s "only path from a prefix to an AVAILABLE row" two paths, both behind `verify_prefix`, and gives sync a skip 4(g) now lists. DescribeBackup, DeleteBackup and RestoreTableFromBackup read the catalog row once more after a legacy not-found (RestoreTableFromBackup after the source read's and after the registration's, taking the row's path), and ListBackups reads the legacy reader before the catalog index, so a replacement that commits between the two reads is answered from its row and never drops the backup from a page; ListBackups then drops an in-catalog summary whose ARN a listed (CREATING or AVAILABLE) catalog row has and keeps the row's, a backup both read listed once (that, or an in-catalog backup whose copy a `backup sync` without the in-catalog skip, a #825 or #880 build during a rolling upgrade, adopted before the migration replaced it). Under `backup-test-hooks` the writer's `after_data_file` and the command's `before_manifest` and `after_manifest` pause it as they pause a job. So item 34's "shares nothing with sync but the insert" does not hold: the command shares `verify_prefix`, sync's row, the claim and the wait, and not the insert. Measured: SIGKILL at each of the three points on SQLite and PostgreSQL left the in-catalog backup whole and no row, and the rerun deleted the copy and migrated it (on PostgreSQL the killed command's advisory lock ended with its session; the rerun now takes the claim once its heartbeat is older than `stale_job_after_secs`); SIGKILL after the manifest and after the first data file, then DeleteBackup, left a prefix that `backup sync` did not adopt and `--all` deleted, the backup staying BackupNotFound (SQLite and PostgreSQL, and PostgreSQL on an S3 store); a first run paused before its manifest whose claim a second run took over (PostgreSQL after the first's catalog session was ended, the second refused until the window had passed; MongoDB with the first stopped past the window and resumed while the catalog was paused) stopped at its re-check, and the second's backup kept its whole prefix and restored every item; a deleted backup's record was removed only by the `--all` that found its prefix clean, after one whose deletion the store refused had kept it (SQLite); a first run stopped (under gdb, all threads) at the link of its first data file, or at the first object of its copy's deletion after a SIGTERM, and resumed after a second run had migrated the backup, left the second run's copy byte for byte as the second wrote it, its restore holding all 45,000 items (PostgreSQL with the first's catalog session ended, and MongoDB); peak RSS flat in the item count on PostgreSQL, 48 to 56 MiB for 1,000 and for 100,000 items on debug builds (75 MiB once, beside a running server), on MongoDB 56 MiB and on Cassandra 55 MiB (both measured on an earlier revision of this change, Cassandra's table without GSIs), and on SQLite 55 to 149 MiB for 1,000 to 250,000 items, the excess its connections' page cache (`cache_size` per connection), bounded by 32 MB times `pool_size` and following the database file's size for a small backup (section 7). The backup manual's legacy section now describes the command, where item 35 had it "not shipped". Also as implemented: after a put whose outcome is unknown the writer reads the key back with `head` and records the object found with the store's metadata, leaving a key the head cannot read to the next run; a failed re-check or fence at a copy's deletion stops the run; a status re-read that fails after a short or failed read fails the backup, which is kept; `finish` reads an AVAILABLE row's prefix back as the copy is read (`verify_prefix`, the manifest's ARN, the count against the in-catalog backup) before it removes an AVAILABLE in-catalog backup, a prefix gone, short or another backup's refusing the backup with the in-catalog backup kept; the SSE description's key ARN is built in the server's region, as the legacy DescribeBackup builds it; the S3 conditional `DeleteObject` re-sends a 409 `ConditionalRequestConflict` as the conditional put does; Cassandra's `list_all` and `list_deleted` scan `backups_by_arn` in pages of 1,000 rows; the stop says the claim is released only when its release succeeded, and after a lost claim that the run no longer holds it; and on every backend only the DeleteBackup that changes an in-catalog backup answers DELETED, every other one, concurrent or later, `BackupNotFoundException` (SQLite re-reads the status under the write lock; MongoDB and Cassandra finish another DeleteBackup's DELETING and answer not found), PostgreSQL's rule since this PR; so the reconciler finishes a Cassandra row that `abandoned_creating_backups` fenced to DELETING through `LegacyBackupReader::delete_fenced` (the second half of `delete`, answering `Ok` for a DELETING or DELETED row), and counts the deletion and writes its audit line, where `delete` would answer it not found. Sections 3, 4(c), 4(f), 4(g) and 7, the PR 10 paragraph, PR 10's maintenance-claim paragraph and transitions, the PR 14 lines and section 10's upgrade-manual row are edited with this item. Not in #821: PR 14's removal of the reader (#749); carrying a backup with a 13-digit id into the store format, refused by design since the format's ids carry their instant; a Cassandra wire leg (its direct tests cover the stream, the listing, the conversion, its lost answer and its stop after the row, the registration's condition, the finish of a row deleted since, and the holder status). + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/design/README.md b/docs/design/README.md index 781e4f2ba..d0d3e97bb 100755 --- a/docs/design/README.md +++ b/docs/design/README.md @@ -38,6 +38,6 @@ This directory contains the authoritative design documents for ExtendDB (extendd Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/dev-image.md b/docs/dev-image.md index 9612855dc..8a254fd39 100644 --- a/docs/dev-image.md +++ b/docs/dev-image.md @@ -154,3 +154,14 @@ condition: service_healthy` work with no extra wiring. but not enforced as capacity. - No TLS and no access control (see dev-mode above): never expose it beyond the local machine, and never store real data in it. + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/differences-from-dynamodb.md b/docs/differences-from-dynamodb.md index 014be75cb..db9b3db30 100755 --- a/docs/differences-from-dynamodb.md +++ b/docs/differences-from-dynamodb.md @@ -258,6 +258,6 @@ and account management. DynamoDB uses the AWS Management Console. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/dynamodb-limits.md b/docs/dynamodb-limits.md index 39167fb48..92bfc362c 100755 --- a/docs/dynamodb-limits.md +++ b/docs/dynamodb-limits.md @@ -191,6 +191,6 @@ The following unenforced limits are tracked in `docs/technical-debt.md`: Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/getting-started.md b/docs/getting-started.md index f2187e4de..7697064dd 100755 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -1518,6 +1518,6 @@ The sample creates three tables (`SampleUsers`, `SampleOrders`, `SampleTournamen Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/local-dev-docker-compose.md b/docs/local-dev-docker-compose.md index 1b8f1784f..d6f31b00a 100644 --- a/docs/local-dev-docker-compose.md +++ b/docs/local-dev-docker-compose.md @@ -143,6 +143,6 @@ aws ecr-public get-login-password --region us-east-1 | \ Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/local-mongodb-setup.md b/docs/local-mongodb-setup.md index 3815e886a..47d55bcb9 100644 --- a/docs/local-mongodb-setup.md +++ b/docs/local-mongodb-setup.md @@ -192,6 +192,6 @@ brew services stop mongodb-community@7.0 Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/local-postgres-setup.md b/docs/local-postgres-setup.md index 66ba7a98e..58c4924e1 100755 --- a/docs/local-postgres-setup.md +++ b/docs/local-postgres-setup.md @@ -88,6 +88,6 @@ export EXTENDDB__STORAGE__POSTGRES__CONNECTION_STRING=\ Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/01-architecture-guide.md b/docs/manuals/01-architecture-guide.md index 401472f38..bb744e8d6 100755 --- a/docs/manuals/01-architecture-guide.md +++ b/docs/manuals/01-architecture-guide.md @@ -327,6 +327,6 @@ The storage backend provides durability, replication, and backup. Use that backe Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/02-design-guide.md b/docs/manuals/02-design-guide.md index af924870f..af9394fe3 100755 --- a/docs/manuals/02-design-guide.md +++ b/docs/manuals/02-design-guide.md @@ -233,6 +233,6 @@ Caching of operational settings is currently unconditional. If issues arise (e.g Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/03-usage-guide.md b/docs/manuals/03-usage-guide.md index 7005f58ed..fe1b4f67b 100755 --- a/docs/manuals/03-usage-guide.md +++ b/docs/manuals/03-usage-guide.md @@ -582,6 +582,6 @@ extenddb reproduces DynamoDB error responses exactly. Common errors: Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/04-quickstart-setup-guide.md b/docs/manuals/04-quickstart-setup-guide.md index 16faece16..3da631150 100755 --- a/docs/manuals/04-quickstart-setup-guide.md +++ b/docs/manuals/04-quickstart-setup-guide.md @@ -423,6 +423,6 @@ See `docs/troubleshooting.md` for the full troubleshooting guide. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/05-admin-guide.md b/docs/manuals/05-admin-guide.md index e44b259bf..fe5f402b7 100755 --- a/docs/manuals/05-admin-guide.md +++ b/docs/manuals/05-admin-guide.md @@ -1143,6 +1143,6 @@ On a new PostgreSQL server (the old one lost with its databases) create the appl Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/06-developer-test-guide.md b/docs/manuals/06-developer-test-guide.md index 22aace5da..d9f043141 100755 --- a/docs/manuals/06-developer-test-guide.md +++ b/docs/manuals/06-developer-test-guide.md @@ -371,6 +371,6 @@ Output goes to `pdfs/` (gitignored). Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/07-upgrade-manual.md b/docs/manuals/07-upgrade-manual.md index eb5a6cfc4..bcd2ea7e7 100755 --- a/docs/manuals/07-upgrade-manual.md +++ b/docs/manuals/07-upgrade-manual.md @@ -1078,6 +1078,6 @@ DescribeStream and GetShardIterator now refuse a client-built `StreamArn` with t Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/08-install-linux.md b/docs/manuals/08-install-linux.md index 536dd29ea..fc95ad326 100755 --- a/docs/manuals/08-install-linux.md +++ b/docs/manuals/08-install-linux.md @@ -211,6 +211,6 @@ See `docs/troubleshooting.md` for the full troubleshooting guide. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/09-install-macos.md b/docs/manuals/09-install-macos.md index 589227642..6b17e1dc5 100755 --- a/docs/manuals/09-install-macos.md +++ b/docs/manuals/09-install-macos.md @@ -197,6 +197,6 @@ See `docs/troubleshooting.md` for the full troubleshooting guide. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/10-security-model.md b/docs/manuals/10-security-model.md index 549bad8c0..3336f8036 100755 --- a/docs/manuals/10-security-model.md +++ b/docs/manuals/10-security-model.md @@ -392,6 +392,6 @@ The encryption key is stored in the catalog database, so a catalog dump contains Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/11-deployment-guide.md b/docs/manuals/11-deployment-guide.md index 6fe264c61..1fa86d217 100755 --- a/docs/manuals/11-deployment-guide.md +++ b/docs/manuals/11-deployment-guide.md @@ -364,6 +364,6 @@ ORDER BY mean_exec_time DESC LIMIT 10; Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/12-extending-extenddb-storage.md b/docs/manuals/12-extending-extenddb-storage.md index 80ab45f05..34434148c 100755 --- a/docs/manuals/12-extending-extenddb-storage.md +++ b/docs/manuals/12-extending-extenddb-storage.md @@ -462,3 +462,14 @@ The PostgreSQL implementation makes backend-specific choices. These are implemen | `CredentialStore` | `auth/src/lib.rs` | `DbCredentialStore` | SigV4 credential lookup | All PostgreSQL-specific code lives in `crates/storage-postgres/`. The `server` crate has no direct database dependencies. Backends register at compile time via the `inventory` crate and are selected by name at startup. + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/13-event-ticketing-demo.md b/docs/manuals/13-event-ticketing-demo.md index b6ee1cdbb..534d92195 100755 --- a/docs/manuals/13-event-ticketing-demo.md +++ b/docs/manuals/13-event-ticketing-demo.md @@ -814,3 +814,14 @@ rm -rf /tmp/extenddb-exports | Reservation TTL | 120 seconds | 900 seconds (15 min) | | Streams polling interval | 1 second | 1–5 seconds | | Export path | `/tmp/extenddb-exports` | `/var/lib/extenddb/exports` | + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/manuals/14-backup-and-restore.md b/docs/manuals/14-backup-and-restore.md index ea7051c55..ce5e180ae 100644 --- a/docs/manuals/14-backup-and-restore.md +++ b/docs/manuals/14-backup-and-restore.md @@ -1138,11 +1138,13 @@ neither path is refused, "Either FilePath or S3Prefix must be provided"). It rea DynamoDB export directly, with `ImportTable` or a restore, is planned (#748) and not in this release; `backup sync` adopts only prefixes with an ExtendDB manifest. +--- + ## License Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/rfcs/0000-mongodb-backend.md b/docs/rfcs/0000-mongodb-backend.md index 4d3678b11..54359b724 100644 --- a/docs/rfcs/0000-mongodb-backend.md +++ b/docs/rfcs/0000-mongodb-backend.md @@ -300,6 +300,6 @@ MongoDB has a native change-data-capture feature (Change Streams) that could bac Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/rfcs/0000-template.md b/docs/rfcs/0000-template.md index 839baca55..cdebdd254 100644 --- a/docs/rfcs/0000-template.md +++ b/docs/rfcs/0000-template.md @@ -53,6 +53,6 @@ projects. What did they get right or wrong? Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/rfcs/0002-backend-plugin-policy.md b/docs/rfcs/0002-backend-plugin-policy.md index 7d67abdb3..1e611c055 100644 --- a/docs/rfcs/0002-backend-plugin-policy.md +++ b/docs/rfcs/0002-backend-plugin-policy.md @@ -345,6 +345,6 @@ Fork entire ExtendDB repo for each backend. Each fork contains frontend + one ba Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/rfcs/0003-backend-acceptance-criteria.md b/docs/rfcs/0003-backend-acceptance-criteria.md index 2c919950e..1a007bf71 100644 --- a/docs/rfcs/0003-backend-acceptance-criteria.md +++ b/docs/rfcs/0003-backend-acceptance-criteria.md @@ -166,6 +166,6 @@ The following scenarios expose the most common failure modes and should be teste Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is -a trademark of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/rfcs/README.md b/docs/rfcs/README.md index 1dfbeb768..5b92f7578 100644 --- a/docs/rfcs/README.md +++ b/docs/rfcs/README.md @@ -55,4 +55,13 @@ you whether an RFC, an ADR, or neither is needed. | [0002](0002-backend-plugin-policy.md) | Backend Plugin Policy | Draft | | | [0003](0003-backend-acceptance-criteria.md) | Backend Acceptance Criteria | Draft | | +--- +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/rfcs/draft-cassandra-backend.md b/docs/rfcs/draft-cassandra-backend.md index 4433af568..b7c418ed7 100644 --- a/docs/rfcs/draft-cassandra-backend.md +++ b/docs/rfcs/draft-cassandra-backend.md @@ -280,3 +280,14 @@ the dependency on stable JSON encoding. item image, so a transaction that crashes between COMMIT and TTL queue reconciliation can leave the item's previous expiration entry in the queue until it comes due. The entry is inert — the worker revalidates before deleting — but it is queue garbage. + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/technical-debt.md b/docs/technical-debt.md index 45e42a6ec..07aec9763 100755 --- a/docs/technical-debt.md +++ b/docs/technical-debt.md @@ -149,6 +149,6 @@ Resolved (split in P94–P96): Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/todo-index.md b/docs/todo-index.md index a5a5f8003..428c744a1 100755 --- a/docs/todo-index.md +++ b/docs/todo-index.md @@ -27,6 +27,6 @@ Regenerated: v0.1.6 (BR-7085) Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 56c073059..05acb27d9 100755 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -1009,6 +1009,6 @@ even after the extension exists. Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. See [LICENSE](../LICENSE) for the full text. -This software is provided "as is" without warranty of any kind. ExtendDB is not -affiliated with, endorsed by, or sponsored by Amazon Web Services. "DynamoDB" is a trademark -of Amazon.com, Inc. +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/verifying-images.md b/docs/verifying-images.md index e0ee8f9c5..5dcd16caa 100644 --- a/docs/verifying-images.md +++ b/docs/verifying-images.md @@ -44,3 +44,14 @@ gh attestation verify oci://docker.io/extenddb/extenddb-postgres@sha256: sbom-amd64.cdx.json ``` + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/docs/versioning.md b/docs/versioning.md index 1390e2050..18add8f69 100644 --- a/docs/versioning.md +++ b/docs/versioning.md @@ -64,3 +64,14 @@ Support covers the stable and beta backends. An experimental backend gets fixes 3. A major release removes the item, no earlier than 6 months after the release that announced it. The same steps apply when a release removes a stable or beta backend, or moves it to a lower tier. A security issue can need a faster change, and its release notes then give the reason. + +--- + +## License + +Copyright 2026 ExtendDB contributors. Licensed under the Apache License, Version 2.0. +See [LICENSE](../LICENSE) for the full text. + +This software is provided "as is" without warranty of any kind. ExtendDB is an open +source project maintained by AWS. It is not Amazon DynamoDB or an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. diff --git a/packaging/npm/README.md b/packaging/npm/README.md index 2851f1a52..7903b25ad 100644 --- a/packaging/npm/README.md +++ b/packaging/npm/README.md @@ -102,10 +102,10 @@ startup; whoever holds it can do anything. Do not expose it beyond localhost and do not keep real data in it. For a durable, TLS-terminated deployment, use [`extenddb/extenddb-postgres`](https://hub.docker.com/r/extenddb/extenddb-postgres). -ExtendDB is an independent open source project managed by Amazon Web -Services. It is not Amazon DynamoDB and does not contain any DynamoDB source -code. "DynamoDB" is a trademark of Amazon.com, Inc. ExtendDB is a clean-room -implementation that speaks the DynamoDB wire protocol. +ExtendDB is an open source project maintained by AWS. It is not Amazon DynamoDB +and does not contain any DynamoDB source code. It is not an AWS service. +"DynamoDB" is a trademark of Amazon.com, Inc. or its affiliates. ExtendDB is a +clean-room implementation that speaks the DynamoDB wire protocol. More at [extenddb.org](https://extenddb.org) and [github.com/ExtendDB/extenddb](https://github.com/ExtendDB/extenddb).