Skip to content

ExtendDB (MongoDB)

v0.1.14 first recorded run

Grade not scored

1 of 1,920 tests got no answer (1 a transport failure or 5xx), so the suite gives no letter or figures for this run. 998 passed, 302 failed, 619 not attempted.

Tier 1 · Core not scored
1 of 507 got no answer
6 of 506 attempted
Tier 2 · Complete 2.6% diverges
24.4% covered 403 unsupported
14 of 130 attempted
Tier 3 · Strict 32.0% diverges
75.5% covered 216 unsupported
282 of 664 attempted

How to run it

Every way ExtendDB (MongoDB) is distributed, each linking to the project's own documentation for it. These are the project's claims, not the suite's measurements.

Needs: a MongoDB 7.0+ replica set, and Docker for the image or a Rust toolchain to build it

Licence: Apache-2.0, licence of ExtendDB (MongoDB) (opens in a new tab)

The PostgreSQL build's server over an external MongoDB replica set rather than PostgreSQL. TLS and SigV4 stay mandatory.

Per-region divergence

This run is not scored, so no region has a divergence figure to show.

Feature support

Measured across the suite's tests for each feature. Compare with other emulators.

ExtendDB (MongoDB) v0.1.14

Core DynamoDB

Vector search
ExtendDB (MongoDB) Vector search: not supported (58 skip)
GSI
ExtendDB (MongoDB) GSI: partially supported (99 pass, 32 fail, 103 skip)
LSI
ExtendDB (MongoDB) LSI: partially supported (79 pass, 15 fail, 95 skip)
PartiQL
ExtendDB (MongoDB) PartiQL: not supported (556 skip)
Transactions
ExtendDB (MongoDB) Transactions: partially supported (128 pass, 56 fail)
Streams
ExtendDB (MongoDB) Streams: supported (18 pass)
TTL
ExtendDB (MongoDB) TTL: supported (7 pass)
Legacy params
ExtendDB (MongoDB) Legacy params: partially supported (50 pass, 84 fail)

Other AWS services

Backups / PITR
ExtendDB (MongoDB) Backups / PITR: supported (5 pass)
Export / import
ExtendDB (MongoDB) Export / import: not supported (2 skip)
Kinesis
ExtendDB (MongoDB) Kinesis: not supported (1 skip)
Resource policies
ExtendDB (MongoDB) Resource policies: not supported (2 skip)
Contributor Insights
ExtendDB (MongoDB) Contributor Insights: not supported (2 skip)
Account API
ExtendDB (MongoDB) Account API: supported (2 pass)

Fully supports

Operation areas this target implements completely - every test passes, nothing skipped. Areas it only partly gets wrong are in “Where it falls short” below; the ones it only partly attempts are in “What it doesn’t attempt”.

  • batchGetItem tier 1
  • batchWriteItem tier 1
  • createTable tier 1
  • deleteItem tier 1
  • deleteTable tier 1
  • describeTable tier 1
  • getItem tier 1
  • listTables tier 1
  • putItem tier 1
  • scan tier 1
  • account tier 2
  • backups tier 2
  • streams tier 2
  • tags tier 2
  • ttl tier 2
  • updateTable tier 2
  • legacy-api tier 3
Only one run recorded so far. The history charts appear once a second run lands.

By operation

Every operation this target implements, with how much of it diverges and how much of it it covers, on the same two axes as the figures above. The counts are fails over the operation's whole size. full, partial, failing, unsupported, not scored. The emulator directory lists support across targets.

Tier 1 - Core

  • batchGetItem 0/15 0.0% 100.0% batchGetItem: supported, diverges on 0.0% of it, covers 100.0% (15 pass)
  • batchWriteItem 0/18 0.0% 100.0% batchWriteItem: supported, diverges on 0.0% of it, covers 100.0% (18 pass)
  • createTable 0/30 0.0% 100.0% createTable: supported, diverges on 0.0% of it, covers 100.0% (30 pass)
  • deleteItem 0/13 0.0% 100.0% deleteItem: supported, diverges on 0.0% of it, covers 100.0% (13 pass)
  • deleteTable 0/3 0.0% 100.0% deleteTable: supported, diverges on 0.0% of it, covers 100.0% (3 pass)
  • describeTable 0/4 0.0% 100.0% describeTable: supported, diverges on 0.0% of it, covers 100.0% (4 pass)
  • getItem 0/39 0.0% 100.0% getItem: supported, diverges on 0.0% of it, covers 100.0% (39 pass)
  • listTables 0/5 0.0% 100.0% listTables: supported, diverges on 0.0% of it, covers 100.0% (5 pass)
  • putItem 0/130 0.0% 100.0% putItem: supported, diverges on 0.0% of it, covers 100.0% (130 pass)
  • query 4/99 4.0% 100.0% query: partially supported, diverges on 4.0% of it, covers 100.0% (95 pass, 4 fail)
  • scan 0/60 0.0% 100.0% scan: supported, diverges on 0.0% of it, covers 100.0% (60 pass)
  • updateItem 1/76 - - updateItem: not scored, because 1 test got no answer (74 pass, 1 fail)
  • updateTable 1/15 6.7% 100.0% updateTable: partially supported, diverges on 6.7% of it, covers 100.0% (14 pass, 1 fail)

Tier 2 - Complete

  • account 0/2 0.0% 100.0% account: supported, diverges on 0.0% of it, covers 100.0% (2 pass)
  • backups 0/5 0.0% 100.0% backups: supported, diverges on 0.0% of it, covers 100.0% (5 pass)
  • contributorInsights 0/2 · 2 skip n/a 0.0% contributorInsights: unsupported, implements none of it (2 skip)
  • export 0/2 · 2 skip n/a 0.0% export: unsupported, implements none of it (2 skip)
  • kinesis 0/1 · 1 skip n/a 0.0% kinesis: unsupported, implements none of it (1 skip)
  • multiAttributeKeys 12/14 85.7% 100.0% multiAttributeKeys: partially supported, diverges on 85.7% of it, covers 100.0% (2 pass, 12 fail)
  • partiql 0/356 · 356 skip n/a 0.0% partiql: unsupported, implements none of it (356 skip)
  • resourcePolicy 0/2 · 2 skip n/a 0.0% resourcePolicy: unsupported, implements none of it (2 skip)
  • streams 0/18 0.0% 100.0% streams: supported, diverges on 0.0% of it, covers 100.0% (18 pass)
  • tags 0/8 0.0% 100.0% tags: supported, diverges on 0.0% of it, covers 100.0% (8 pass)
  • transactions 2/62 3.2% 100.0% transactions: partially supported, diverges on 3.2% of it, covers 100.0% (60 pass, 2 fail)
  • ttl 0/7 0.0% 100.0% ttl: supported, diverges on 0.0% of it, covers 100.0% (7 pass)
  • updateTable 0/14 0.0% 100.0% updateTable: supported, diverges on 0.0% of it, covers 100.0% (14 pass)
  • vectorSearch 0/40 · 40 skip n/a 0.0% vectorSearch: unsupported, implements none of it (40 skip)

Tier 3 - Strict

  • error-messages 107/451 · 195 skip 23.7% 56.8% error-messages: partially supported, diverges on 23.7% of it, covers 56.8% (149 pass, 107 fail, 195 skip)
  • legacy-api 0/42 0.0% 100.0% legacy-api: supported, diverges on 0.0% of it, covers 100.0% (42 pass)
  • limits 68/214 · 5 skip 31.8% 97.7% limits: partially supported, diverges on 31.8% of it, covers 97.7% (141 pass, 68 fail, 5 skip)
  • validation-ordering 107/173 · 16 skip 61.8% 90.8% validation-ordering: partially supported, diverges on 61.8% of it, covers 90.8% (50 pass, 107 fail, 16 skip)

Where it falls short

Operations ExtendDB (MongoDB) implements and answers differently from real DynamoDB, biggest gap first. They would count towards its divergence figure, but this run is not scored. Open one for the exact tests, or see the conformance suite.

  • error-messages Tier 3 107 diverging 195 not attempted
    View these tests in the suite →
    • BatchGetItem - exact error messages malformed table name: full map-keys constraint message source:179
    • BatchWriteItem - exact error messages item without the partition key: full schema-mismatch message source:157
    • BatchWriteItem - exact error messages delete key without the partition key: full schema-mismatch message source:157
    • BatchWriteItem - exact error messages malformed table name: anchored regex on the map-keys constraint source:262
    • Table and index operations measure a name table names, in UTF-16 units CreateTable finds 128 emoji too long source:80
    • Table and index operations measure a name table names, in UTF-16 units DescribeTable finds 128 emoji too long source:90
    • Table and index operations measure a name table names, in UTF-16 units DeleteTable finds 128 emoji too long source:100
    • Table and index operations measure a name table names, in UTF-16 units UpdateTable does not find two emoji too short source:60
    • Table and index operations measure a name table names, in UTF-16 units UpdateTable finds 128 emoji too long source:60
    • Table and index operations measure a name ListTables and index names, in characters ListTables finds two emoji too short source:39
    • Table and index operations measure a name ListTables and index names, in characters ListTables does not find 128 emoji too long source:161
    • Table and index operations measure a name ListTables and index names, in characters CreateTable finds a GSI name of two emoji too short source:39
    • Table and index operations measure a name ListTables and index names, in characters CreateTable does not find a GSI name of 128 emoji too long source:176
    • Table and index operations measure a name ListTables and index names, in characters CreateTable finds an LSI name of two emoji too short source:39
    • Table and index operations measure a name ListTables and index names, in characters CreateTable does not find an LSI name of 128 emoji too long source:191
    • Table and index operations measure a name ListTables and index names, in characters UpdateTable finds a new GSI name of two emoji too short source:39
    • Table and index operations measure a name ListTables and index names, in characters UpdateTable does not find a new GSI name of 128 emoji too long source:202
    • DeleteItem - request validation envelope ExpressionAttributeValues or ExpressionAttributeNames without an expression source:120
    • DeleteItem - request validation envelope an empty ExpressionAttributeValues or ExpressionAttributeNames map source:133
    • DeleteItem - request validation envelope an empty ConditionExpression source:115
    • DeleteItem - request validation envelope ReturnValues ALL_NEW or UPDATED_NEW source:142
    • DeleteItem - request validation envelope every malformed Expected condition source:112
    • UpdateItem - index key error messages empty-binary index key value: full secondary-index-key message source:150
    • Leading underscore - exact error messages in a Query FilterExpression source:28
    • Leading underscore - exact error messages in a Scan FilterExpression source:28
    • Leading underscore - exact error messages in a ProjectionExpression source:28
    • Leading underscore - exact error messages as the partition key in a KeyConditionExpression source:69
    • Leading underscore - exact error messages inside begins_with in a KeyConditionExpression source:28
    • Leading underscore - exact error messages in a KeyConditionExpression on an index source:99
    • Leading underscore - exact error messages in a ConditionExpression source:28
    • Leading underscore - exact error messages in an UpdateExpression source:28
    • PutItem - request validation envelope ExpressionAttributeValues or ExpressionAttributeNames without an expression source:400
    • PutItem - request validation envelope an empty ConditionExpression source:395
    • PutItem - request validation envelope a malformed Expected condition source:392
    • Query - KeyConditionExpression operand types begins_with on a string sort key with a number operand - exact message source:46
    • Query - KeyConditionExpression operand types begins_with on a string sort key with a boolean operand - exact message source:46
    • Query - KeyConditionExpression operand types begins_with on a number sort key with a number operand - exact message source:46
    • Query - KeyConditionExpression operand types begins_with on a number sort key with a string operand fails the schema check - exact message source:30
    • Query - KeyConditionExpression operand types an ordering comparison with a boolean operand - exact message source:45
    • Query - KeyConditionExpression operand types an ordering comparison written value first - exact message source:45
    • Query - KeyConditionExpression operand types BETWEEN with boolean bounds - exact message source:45
    • Query - KeyConditionExpression operand types equality with a boolean fails the schema check - exact message source:45
    • Query - KeyConditionExpression operand types two conditions on the sort key - exact message source:46
    • Query - KeyConditionExpression operand types three conditions naming three attributes on a two-attribute key - exact message source:30
    • Query - multi-attribute GSI key exact error messages a gap in the RANGE attributes - exact message source:76
    • Query - multi-attribute GSI key exact error messages a range condition before the last attribute named - exact message source:76
    • Query - multi-attribute GSI key exact error messages skipping the first RANGE attribute - exact message source:65
    • Scan - exact error messages Segment >= TotalSegments: full out-of-range error source:62
    • Scan - exact error messages Limit of 0: full minimum-value error source:103
    • Scan - exact error messages negative Segment: full minimum-value error source:127
    • Scan - exact error messages malformed ExclusiveStartKey: long schema-mismatch error source:211
    • Scan - exact error messages Select SPECIFIC_ATTRIBUTES without ProjectionExpression: full required-projection message source:236
    • Item operations count a table name in characters PutItem does not find 200 accented letters too long source:57
    • Item operations count a table name in characters, split by region PutItem reports only the length for two accented letters source:67
    • Item operations count a table name in characters, split by region PutItem finds two emoji too short source:72
    • Item operations count a table name in characters, split by region PutItem does not find 128 emoji too long source:77
    • Item operations count a table name in characters, split by region UpdateItem finds two emoji too short, after the pattern source:82
    • Item operations count a table name in characters, split by region GetItem finds two emoji too short source:38
    • Item operations count a table name in characters, split by region GetItem does not find 128 emoji too long source:38
    • Item operations count a table name in characters, split by region DeleteItem finds two emoji too short source:99
    • Item operations count a table name in characters, split by region DeleteItem does not find 128 emoji too long source:104
    • Item operations count a table name in characters, split by region Query finds two emoji too short source:38
    • Item operations count a table name in characters, split by region Query does not find 128 emoji too long source:38
    • Item operations count a table name in characters, split by region Scan finds two emoji too short source:38
    • Item operations count a table name in characters, split by region Scan does not find 128 emoji too long source:38
    • TransactGetItems - exact error messages malformed table name: top-level ValidationException naming the member source:165
    • TransactGetItems - exact error messages malformed table name on the second Get: the message names its position source:185
    • TransactWriteItems - index key error messages Put empty-string index key: top-level ValidationException source:76
    • TransactWriteItems - index key error messages Update empty-string index key: top-level ValidationException source:76
    • TransactWriteItems - index key error messages Put empty-binary index key: top-level ValidationException source:76
    • TransactWriteItems - index key error messages Update empty-binary index key: top-level ValidationException source:76
    • TransactWriteItems - exact error messages Update wrong-typed Key: cancelled with schema-mismatch reason source:282
    • TransactWriteItems - exact error messages Update non-scalar Key: cancelled with schema-mismatch reason source:282
    • TransactWriteItems - exact error messages Delete wrong-typed Key: cancelled with schema-mismatch reason source:282
    • TransactWriteItems - exact error messages Delete non-scalar Key: cancelled with schema-mismatch reason source:282
    • TransactWriteItems - exact error messages ConditionCheck wrong-typed Key: cancelled with schema-mismatch reason source:282
    • TransactWriteItems - exact error messages ConditionCheck non-scalar Key: cancelled with schema-mismatch reason source:282
    • TransactWriteItems - exact error messages Put malformed table name: top-level message naming the member source:295
    • TransactWriteItems - exact error messages Update malformed table name on the second action: top-level message naming the member source:295
    • TransactWriteItems - exact error messages Delete malformed table name: top-level message naming the member source:295
    • TransactWriteItems - exact error messages ConditionCheck malformed table name: top-level message naming the member source:295
    • TransactWriteItems - exact error messages Put empty ConditionExpression: top-level empty-expression message source:294
    • TransactWriteItems - exact error messages Delete empty ConditionExpression: top-level empty-expression message source:294
    • TransactWriteItems - exact error messages ConditionCheck empty ConditionExpression: top-level empty-expression message source:296
    • TransactWriteItems - exact error messages ConditionCheck malformed ConditionExpression: top-level syntax message source:296
    • TransactWriteItems - exact error messages action with no operation: top-level message source:491
    • UpdateItem - exact error messages undefined value in the ConditionExpression beside a defined one: full error string source:152
    • Number values - messages by operation PutItem refuses every malformed number in an item inside the validation envelope source:120
    • Number values - messages by operation PutItem refuses a malformed number set member and a nested number inside the envelope source:126
    • Number values - messages by operation PutItem refuses a malformed number in a condition value inside the envelope source:65
    • Number values - messages by operation PutItem checks the numbers in Expected values and writes nothing source:65
    • Number values - messages by operation UpdateItem refuses a malformed number in a value, in AttributeUpdates and in the key inside the envelope source:161
    • Number values - messages by operation DeleteItem refuses a malformed number in a condition value and in the key inside the envelope, with no wrapper source:65
    • Number values - messages by operation GetItem, BatchGetItem and Query refuse a malformed number bare, in the current wording source:185
    • Number values - messages by operation BatchWriteItem refuses a malformed number bare, in one layer for every shape source:191
    • Number values - transactions by region TransactWriteItems refuses a malformed number in a Put item up front source:220
    • Number values - transactions by region TransactWriteItems refuses a malformed number in an Update value up front source:233
    • Number values - transactions by region TransactGetItems refuses a malformed number in a key up front source:65
    • Duplicate set members - messages by operation PutItem refuses a duplicate in an item, a condition value and an Expected value inside the envelope source:290
    • Duplicate set members - messages by operation UpdateItem refuses a duplicate in a condition value, AttributeUpdates and the key inside the envelope source:312
    • Duplicate set members - messages by operation DeleteItem refuses a duplicate in the key inside the envelope source:317
    • Duplicate set members - messages by operation GetItem and BatchGetItem refuse a duplicate in the key bare, in the current wording source:323
    • Duplicate set members - messages by operation Query refuses a duplicate in a key value, a filter value, ExclusiveStartKey and QueryFilter bare, with no wrapper source:354
    • Duplicate set members - messages by operation BatchWriteItem refuses a duplicate in an item and a delete key bare, in one layer for both source:370
    • Duplicate set members - transactions by region TransactWriteItems refuses a duplicate in a Put item and a Delete key up front source:388
    • Duplicate set members - transactions by region TransactWriteItems refuses a duplicate in a condition or update value of every action type up front source:406
    • Duplicate set members - transactions by region TransactGetItems refuses a duplicate in a key up front source:413
    • PartiQL - exact error messages DELETE RETURNING MODIFIED OLD * - exact message
    • PartiQL - exact error messages DELETE RETURNING ALL NEW * - exact message
    • PartiQL - exact error messages DELETE RETURNING MODIFIED NEW * - exact message
    • PartiQL - exact error messages ExecuteTransaction with a RETURNING member - exact message
    • PartiQL - exact error messages an ordering comparison on an unordered operand - exact message
    • PartiQL functions - exact error messages attribute_exists with a string literal - exact message
    • PartiQL functions - exact error messages attribute_exists with a parameter - exact message
    • PartiQL functions - exact error messages attribute_exists with no operand - exact message
    • PartiQL functions - exact error messages attribute_exists with two operands - exact message
    • PartiQL functions - exact error messages attribute_exists as a SELECT projection - exact message
    • PartiQL functions - exact error messages EXISTS(path) in a WHERE is not a function - exact message
    • PartiQL functions - exact error messages a path through an attribute named inner - exact message
    • PartiQL functions - exact error messages a SELECT in ExecuteTransaction whose WHERE uses attribute_exists - exact message
    • PartiQL functions - exact error messages a SELECT in BatchExecuteStatement whose WHERE uses attribute_exists - exact message
    • PartiQL functions - exact error messages EXISTS(SELECT ...) with no further condition in ExecuteTransaction - exact message
    • PartiQL functions - exact error messages set_add assigned to another attribute - exact message
    • PartiQL functions - exact error messages set_add whose first argument is not a path - exact message
    • PartiQL functions - exact error messages set_add with a string to add - exact message
    • PartiQL functions - exact error messages set_add with a list to add - exact message
    • PartiQL functions - exact error messages set_add with one argument - exact message
    • PartiQL functions - exact error messages set_add with three arguments - exact message
    • PartiQL functions - exact error messages set_add of a number to a string set - exact message
    • PartiQL functions - exact error messages set_add to an attribute that is not a set - exact message
    • PartiQL functions - exact error messages set_add of a set literal with a repeated member - exact message
    • PartiQL functions - exact error messages set_add of an empty set literal - exact message
    • PartiQL functions - exact error messages set_add on a path through an attribute named inner - exact message
    • PartiQL functions - exact error messages set_add in a SELECT WHERE - exact message
    • PartiQL functions - exact error messages set_add in an INSERT value - exact message
    • PartiQL functions - exact error messages set_delete assigned to another attribute - exact message
    • PartiQL functions - exact error messages set_delete with a string to remove - exact message
    • PartiQL functions - exact error messages set_delete of a number from a string set - exact message
    • PartiQL grammar - exact error messages a token after a SELECT WHERE clause - exact message
    • PartiQL grammar - exact error messages a number split from its exponent - exact message
    • PartiQL grammar - exact error messages a token after an INSERT item literal - exact message
    • PartiQL grammar - exact error messages a token after an UPDATE WHERE clause - exact message
    • PartiQL grammar - exact error messages a token after a DELETE WHERE clause - exact message
    • PartiQL grammar - exact error messages a stray closing parenthesis - exact message
    • PartiQL grammar - exact error messages ORDER BY on a DELETE - exact message
    • PartiQL grammar - exact error messages ORDER BY ahead of WHERE - exact message
    • PartiQL grammar - exact error messages an exponent that does not fit a 32-bit integer - nothing after the colon
    • PartiQL grammar - exact error messages a far larger exponent - nothing after the colon
    • PartiQL grammar - exact error messages an exponent that fits but leaves a scale that does not - nothing after the colon
    • PartiQL grammar - exact error messages a hash comment - nothing after the colon
    • PartiQL grammar - exact error messages an unterminated block comment - nothing after the colon
    • PartiQL grammar - exact error messages an alias on a SELECT - exact message
    • PartiQL grammar - exact error messages an AS alias on a SELECT - exact message
    • PartiQL grammar - exact error messages an alias on an UPDATE - exact message
    • PartiQL grammar - exact error messages an alias on a DELETE - exact message
    • PartiQL grammar - exact error messages an alias on an INSERT is a leftover token - exact message
    • PartiQL grammar - exact error messages a WHERE literal above the largest number - exact message
    • PartiQL grammar - exact error messages a WHERE literal below the smallest number - exact message
    • PartiQL grammar - exact error messages a WHERE literal with 39 significant digits - exact message
    • PartiQL grammar - exact error messages an INSERT literal above the largest number - exact message
    • PartiQL grammar - exact error messages an UPDATE SET literal below the smallest number - exact message
    • PartiQL grammar - exact error messages a literal inside a map names its path - exact message
    • PartiQL grammar - exact error messages a literal inside a list names its index - exact message
    • PartiQL grammar - exact error messages WHERE at the end of a SELECT - exact message
    • PartiQL grammar - exact error messages WHERE then a semicolon - exact message
    • PartiQL grammar - exact error messages WHERE then spaces - exact message
    • PartiQL grammar - exact error messages WHERE after a projection - exact message
    • PartiQL grammar - exact error messages WHERE at the end of an UPDATE - exact message
    • PartiQL grammar - exact error messages WHERE at the end of a DELETE - exact message
    • PartiQL grammar - exact error messages WHERE NOT with nothing after it - exact message
    • PartiQL grammar - exact error messages WHERE ( with nothing after it - exact message
    • PartiQL grammar - exact error messages WHERE at the end, on a table that does not exist - exact message
    • PartiQL grammar - exact error messages a condition ending in AND - exact message
    • PartiQL grammar - exact error messages a condition ending in OR - exact message
    • PartiQL grammar - exact error messages WHERE followed by ORDER BY - exact message
    • PartiQL grammar - exact error messages an empty WHERE in ExecuteTransaction - exact message
    • PartiQL grammar - exact error messages an empty WHERE in BatchExecuteStatement - exact message
    • PartiQL grammar - exact error messages IS INT4 parses as a type test - exact message
    • PartiQL grammar - exact error messages IS INT8 parses as a type test - exact message
    • PartiQL grammar - exact error messages IS DOUBLE PRECISION parses as a type test - exact message
    • PartiQL grammar - exact error messages IS CHARACTER VARYING parses as a type test - exact message
    • PartiQL grammar - exact error messages IS with a name that is not a type, in a WHERE - exact message
    • PartiQL grammar - exact error messages IS where a WHERE condition should start - exact message
    • PartiQL grammar - exact error messages LIKE where a comparison operand should start - exact message
    • PartiQL grammar - exact error messages DELETE FROM with no table - exact message
    • PartiQL grammar - exact error messages DELETE FROM then spaces with no table - exact message
    • PartiQL grammar - exact error messages DELETE FROM then a semicolon with no table - exact message
    • PartiQL grammar - exact error messages DELETE FROM then WHERE with no table - exact message
    • PartiQL grammar - exact error messages SELECT * FROM with no table - exact message
    • PartiQL grammar - exact error messages FROM ... SET with no WHERE - exact message
    • PartiQL grammar - exact error messages FROM ... REMOVE with no WHERE - exact message
    • PartiQL grammar - exact error messages FROM ... WHERE on a non-key attribute ... SET - exact message
    • PartiQL grammar - exact error messages FROM ... SET with the WHERE after it - exact message
    • PartiQL grammar - exact error messages FROM ... SET ... WHERE ... SET - exact message
    • PartiQL grammar - exact error messages FROM ... WHERE ... SET on a table that does not exist - exact error
    • PartiQL grammar - exact error messages an OR branch with a non-key equality beside a sort-key branch - exact message
    • PartiQL grammar - exact error messages an OR branch with a non-key <> beside a sort-key branch - exact message
    • PartiQL grammar - exact error messages OR branches whose sort-key ranges meet - exact message
    • PartiQL grammar - exact error messages an OR beside a sort-key equality with a non-key branch - exact message
    • PartiQL grammar - exact error messages 1 (NOT sk = ... OR x = ...) pairs - exact message
    • PartiQL grammar - exact error messages 2 (NOT sk = ... OR x = ...) pairs - exact message
    • PartiQL grammar - exact error messages 9 (NOT sk = ... OR x = ...) pairs - exact message
    • PartiQL grammar - exact error messages a string partition key given the same number twice - exact message
    • PartiQL grammar - exact error messages a string partition key given one number - exact message
    • PartiQL grammar - exact error messages a partition key given a boolean - exact message
    • PartiQL grammar - exact error messages a partition key given a boolean beside two sort-key equalities - exact message
    • PartiQL grammar - exact error messages ORDER BY over two branches on one partition - exact message
    • PartiQL grammar - exact error messages ORDER BY over a literal branch and a parameter branch on one partition - exact message
    • PartiQL grammar - exact error messages ORDER BY on the sort key over two partitions - exact message
    • PartiQL grammar - exact error messages a Limit of 0 - exact message
    • PartiQL grammar - exact error messages a Limit of -1 - exact message
    • PartiQL grammar - exact error messages a Limit sent as a string - exact error
    • PartiQL index qualifier - exact error messages unprojected filter attribute on a GSI - exact message
    • PartiQL index qualifier - exact error messages unprojected filter attribute on an LSI - same wording, no Local prefix
    • PartiQL index qualifier - exact error messages unprojected attribute in an OR filter on a KEYS_ONLY GSI, keyed on one key value - exact message
    • PartiQL index qualifier - exact error messages unprojected attribute in an OR filter on a KEYS_ONLY GSI, keyed on an IN list - exact message
    • PartiQL index qualifier - exact error messages unprojected projection attribute on a GSI - exact message
    • PartiQL index qualifier - exact error messages unprojected projection attribute on an unkeyed GSI scan - exact message
    • PartiQL index qualifier - exact error messages two unprojected projection attributes on a GSI, named as listed - the same list
    • PartiQL index qualifier - exact error messages two unprojected projection attributes on a GSI, named reversed - the same list
    • PartiQL index qualifier - exact error messages a qualifier naming no index - exact message, with no name appended
    • PartiQL index qualifier - exact error messages a qualifier naming the table itself - same message
    • PartiQL index qualifier - exact error messages a three-component path - exact message
    • PartiQL index qualifier - exact error messages an empty index component - exact message
    • PartiQL index qualifier - exact error messages ConsistentRead against a GSI qualifier - exact message
    • PartiQL index qualifier - exact error messages an unknown index with ConsistentRead - the unknown index is reported
    • PartiQL index qualifier - exact error messages an index-qualified read inside a transaction - exact message
    • PartiQL - multi-attribute index exact error messages a SELECT on a GSI with two HASH and two RANGE attributes - exact message
    • PartiQL - multi-attribute index exact error messages a SELECT on a GSI with two HASH attributes and one RANGE - exact message
    • PartiQL - multi-attribute index exact error messages a SELECT with ORDER BY on a multi-attribute GSI - exact message
    • PartiQL - multi-attribute index exact error messages a statement that breaks off reports its syntax error ahead of the refusal
    • PartiQL - multi-attribute index exact error messages a number literal that cannot be converted is reported ahead of the refusal
    • PartiQL - multi-attribute index exact error messages a parameter that cannot be converted to a number is reported ahead of the refusal
    • PartiQL - multi-attribute index exact error messages the refusal is reported ahead of a key type mismatch, a non-key WHERE, a missing WHERE and COUNT(*)
    • PartiQL - multi-attribute index exact error messages in a BatchExecuteStatement only the statement reading the index fails, ahead of the key-only rule
    • PartiQL parameters - numbers - exact error messages the parameter 1e99999999999 in a WHERE comparison cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e99999999999 in an INSERT value cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e99999999999 in an UPDATE SET cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e99999999999 in a key cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter -1e99999999999 in a WHERE comparison cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter -1e99999999999 in an INSERT value cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter -1e99999999999 in an UPDATE SET cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter -1e99999999999 in a key cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e-99999999999 in a WHERE comparison cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e-99999999999 in an INSERT value cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e-99999999999 in an UPDATE SET cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e-99999999999 in a key cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483648 in a WHERE comparison cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483648 in an INSERT value cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483648 in an UPDATE SET cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483648 in a key cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e-2147483648 in a WHERE comparison cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e-2147483648 in an INSERT value cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e-2147483648 in an UPDATE SET cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e-2147483648 in a key cannot be converted - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483647 in a WHERE comparison underflows - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483647 in an INSERT value underflows - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483647 in an UPDATE SET underflows - exact message
    • PartiQL parameters - numbers - exact error messages the parameter 1e2147483647 in a key underflows - exact message
    • PartiQL parameters - numbers - exact error messages an empty number parameter in a WHERE comparison - exact message
    • PartiQL parameters - numbers - exact error messages an empty number parameter in an INSERT value - exact message
    • PartiQL parameters - numbers - exact error messages an empty number parameter in an UPDATE SET - exact message
    • PartiQL parameters - numbers - exact error messages an empty number parameter in a key - exact message
    • PartiQL parameters - numbers - exact error messages an unconvertible number inside a list parameter - exact message
    • PartiQL parameters - numbers - exact error messages an unconvertible number inside a map parameter - exact message
    • PartiQL parameters - numbers - exact error messages an unconvertible member of a number set parameter - exact message
    • PartiQL parameters - numbers - exact error messages an unconvertible number in ExecuteTransaction - exact message
    • PartiQL parameters - numbers - exact error messages an unconvertible number in BatchExecuteStatement - exact message
    • PartiQL parameters - numbers - exact error messages nested 40 levels a deep parameter before an unconvertible one - exact message
    • PartiQL parameters - numbers - exact error messages nested 40 levels an unconvertible parameter before a deep one - exact message
    • PartiQL parameters - numbers - exact error messages nested 40 levels a deep member of a map before an unconvertible one - exact message
    • PartiQL parameters - numbers - exact error messages nested 40 levels an unconvertible member of a map before a deep one - exact message
    • PartiQL parameters - numbers - exact error messages nested 40 levels an unconvertible number at the bottom of a deep value - exact message
    • PartiQL parameters - numbers - exact error messages nested 40 levels a deep parameter before one past the largest number - exact message
    • PartiQL parameters - numbers - exact error messages nested 40 levels a deep parameter before an unconvertible one, in ExecuteTransaction - exact message
    • PartiQL parameters - numbers - exact error messages nested 40 levels a deep parameter before an unconvertible one, in BatchExecuteStatement - exact message
    • PartiQL parameters - numbers - exact error messages nested 100 levels a deep parameter before an unconvertible one - exact message
    • PartiQL parameters - numbers - exact error messages nested 100 levels an unconvertible parameter before a deep one - exact message
    • PartiQL parameters - numbers - exact error messages nested 100 levels a deep member of a map before an unconvertible one - exact message
    • PartiQL parameters - numbers - exact error messages nested 100 levels an unconvertible member of a map before a deep one - exact message
    • PartiQL parameters - numbers - exact error messages nested 100 levels an unconvertible number at the bottom of a deep value - exact message
    • PartiQL parameters - numbers - exact error messages nested 100 levels a deep parameter before one past the largest number - exact message
    • PartiQL parameters - numbers - exact error messages nested 100 levels a deep parameter before an unconvertible one, in ExecuteTransaction - exact message
    • PartiQL parameters - numbers - exact error messages nested 100 levels a deep parameter before an unconvertible one, in BatchExecuteStatement - exact message
    • SearchVectors - exact error messages TopK above the maximum
    • SearchVectors - exact error messages missing SearchConditionExpression against a HASH-schema index
    • SearchVectors - exact error messages non-equality comparator on the HASH element
    • SearchVectors - exact error messages non-equality comparator on an INLINE_FILTER element
    • SearchVectors - exact error messages query vector dimension mismatch
    • SearchVectors - exact error messages condition attribute outside the SearchSchema
    • SearchVectors - exact error messages L-wrapped search vector
    • SearchVectors - request shape errors refuses an explicit null member as a SerializationException
    • SearchVectors - request shape errors names a missing TableName as a missing field, before a too-short IndexName
    • CreateTable vector indexes - exact error messages vector index on a provisioned table
    • CreateTable vector indexes - exact error messages SearchSchema attribute missing from AttributeDefinitions
    • CreateTable vector indexes - exact error messages Dimensions above the 4096 maximum
    • CreateTable vector indexes - exact error messages more vector indexes than the per-table limit
    • CreateTable vector indexes - exact error messages two indexes on one attribute with different Dimensions
    • PutItem vector writes - exact error messages vector with the wrong dimension count
    • PutItem vector writes - exact error messages vector element that is not a number, naming the element
    • PutItem vector writes - exact error messages vector attribute that is not a list
    • PutItem vector writes - exact error messages empty string in the SearchSchema HASH attribute
  • validation-ordering Tier 3 107 diverging 16 not attempted
    View these tests in the suite →
    • Batch operations - enum and ordering checks BatchWriteItem reports both unknown enums in one message, ReturnConsumedCapacity first source:188
    • Batch operations - enum and ordering checks BatchGetItem reports a malformed table name and an unknown ReturnConsumedCapacity together source:256
    • CreateTable - index name errors across index kinds lists the GSI error before the LSI error when the request lists the LSI first source:207
    • CreateTable - index name errors across index kinds lists the GSI error first even when the LSI name sorts first source:214
    • Deep requests - legacy conditions PutItem reports XOR in the older enum wording ahead of an Expected value nested 100 levels source:75
    • Deep requests - legacy conditions UpdateItem reports XOR in the older enum wording ahead of an Expected value nested 100 levels source:75
    • Deep requests - TransactWriteItems action order reports a Put item nested 40 levels before an empty attribute name in a later Put source:75
    • Deep requests - TransactWriteItems action order reports an empty attribute name before a Put item nested 100 levels in a later Put source:75
    • Deep requests - TransactWriteItems action order reports a top-level empty attribute name before a value nested 100 levels in the same item, in either order source:75
    • Deep requests - TransactWriteItems action order refuses a value nested 40 levels beside an empty map key inside the same item source:75
    • Deep requests - TransactWriteItems action order reports an empty attribute name before a later ConditionCheck value nested 100 levels source:75
    • Deep requests - TransactWriteItems action order reports an earlier ConditionCheck value nested 40 levels before a later empty attribute name source:75
    • Deep requests - TransactWriteItems action order reports an earlier Update value nested 40 levels before a later empty attribute name source:75
    • Deep requests - TransactWriteItems action order reports a Delete key nested 40 levels before a later Put condition syntax error source:75
    • Deep requests - TransactWriteItems action order reports a ConditionCheck key nested 40 levels before a later Update unused value source:75
    • Deep requests - TransactWriteItems action order reports a Put condition syntax error before a later Delete key nested 100 levels source:75
    • Deep requests - TransactWriteItems action order reports a condition syntax error before the same Delete key nested 100 levels source:75
    • Deep requests - TransactWriteItems action order reports an oversized condition before the same Delete key nested 100 levels source:75
    • Deep requests - TransactWriteItems action order reports an oversized UpdateExpression before a later ConditionCheck key nested 100 levels source:75
    • Deep requests - TransactWriteItems action order reports an unused value before a later ConditionCheck key nested 100 levels source:75
    • Deep requests - DeleteItem ReturnValues refuses an unknown ReturnValues in the older wording when the condition value is nested 63 levels source:75
    • Deep requests - DeleteItem ReturnValues refuses an unknown ReturnValues in the older wording when an Expected value is nested 63 levels source:75
    • Deep requests - DeleteItem ReturnValues refuses an unknown ReturnValues in the older wording when the key is nested 100 levels source:75
    • Deep requests - DeleteItem ReturnValues refuses UPDATED_NEW with the bare ReturnValues message ahead of a condition value nested 100 levels source:75
    • Deep writes list every bad member in order PutItem joins a bad ReturnValues and XOR source:75
    • Deep writes list every bad member in order PutItem lists ReturnValues, XOR, then a bad ReturnConsumedCapacity source:75
    • Deep writes list every bad member in order PutItem lists ReturnValues, XOR, then a bad ReturnItemCollectionMetrics source:75
    • Deep writes list every bad member in order PutItem lists ReturnValues then ReturnConsumedCapacity without XOR source:75
    • Deep writes list every bad member in order PutItem leaves a valid ReturnValues out of the list source:75
    • Deep writes list every bad member in order PutItem lists all five bad members in order source:75
    • Deep writes list every bad member in order PutItem lists a missing Item third among all five bad members source:75
    • Deep writes list every bad member in order PutItem reads a null Item as missing source:75
    • Deep writes list every bad member in order UpdateItem joins a bad ReturnValues and XOR source:75
    • Deep writes list every bad member in order UpdateItem lists a bad ReturnConsumedCapacity ahead of ReturnValues and XOR source:75
    • Deep writes list every bad member in order UpdateItem lists ReturnValues, XOR, then a bad ReturnItemCollectionMetrics source:75
    • Deep writes list every bad member in order UpdateItem lists ReturnConsumedCapacity, ReturnValues, XOR, then ReturnItemCollectionMetrics source:75
    • Deep writes list every bad member in order UpdateItem lists all five bad members in order source:75
    • Deep writes list every bad member in order UpdateItem lists a missing Key last among all five bad members source:75
    • Deep writes list every bad member in order UpdateItem lists a missing Key after ReturnValues and XOR source:75
    • Deep writes list every bad member in order UpdateItem reads a null Key as missing source:75
    • Deep writes list every bad member in order UpdateItem keeps the envelope for a bad ReturnConsumedCapacity alone source:75
    • Deep writes list every bad member in order UpdateItem keeps the envelope for a bad ReturnValuesOnConditionCheckFailure alone source:75
    • Deep writes list every bad member in order UpdateItem treats a value that reads like an error header as a plain value source:75
    • Deep writes list every bad member in order DeleteItem joins a bad ReturnValues and XOR source:75
    • Deep writes list every bad member in order DeleteItem lists ReturnValues, XOR, then a bad ReturnConsumedCapacity source:75
    • Deep writes list every bad member in order DeleteItem lists ReturnValues, XOR, then a bad ReturnItemCollectionMetrics source:75
    • Deep writes list every bad member in order DeleteItem lists ReturnValues, XOR, ReturnConsumedCapacity, then ReturnItemCollectionMetrics source:75
    • Deep writes list every bad member in order DeleteItem lists ReturnValues, XOR, then a bad ReturnValuesOnConditionCheckFailure source:75
    • Deep writes list every bad member in order DeleteItem lists all five bad members in order source:75
    • Deep writes list every bad member in order DeleteItem lists a missing Key last among all five bad members source:75
    • Deep writes list every bad member in order DeleteItem reads a null Key as missing source:75
    • Deep writes list every bad member in order DeleteItem reports XOR alone ahead of the nesting error source:75
    • Deep writes list every bad member in order DeleteItem reports only XOR beside a ReturnValues of ALL_NEW source:75
    • Deep writes list every bad member in order DeleteItem drops a ReturnValues of ALL_NEW beside a bad ReturnConsumedCapacity source:75
    • Deep writes list every bad member in order DeleteItem keeps a value holding "; " as one error source:75
    • Deep writes check the table name in two stages PutItem lists a missing name after a bad ReturnValues source:75
    • Deep writes check the table name in two stages PutItem reports a missing name alone in the envelope source:75
    • Deep writes check the table name in two stages PutItem lists a missing name last, after every bad member and the missing Item source:75
    • Deep writes check the table name in two stages PutItem lists an empty name as a member error after a bad ReturnValues source:75
    • Deep writes check the table name in two stages PutItem lists an empty name after a missing Item source:75
    • Deep writes check the table name in two stages PutItem drops a short name beside a bad ReturnValues source:75
    • Deep writes check the table name in two stages PutItem drops a name with bad characters beside a bad ReturnValues source:75
    • Deep writes check the table name in two stages PutItem drops a short name beside a missing Item source:75
    • Deep writes check the table name in two stages PutItem drops a 300-character name beside XOR and a bad ReturnValues source:75
    • Deep writes check the table name in two stages PutItem reports a short name once every member passes source:75
    • Deep writes check the table name in two stages PutItem lists the length then the pattern for a short name with bad characters source:75
    • Deep writes check the table name in two stages PutItem lists the length then the pattern for a long name with bad characters source:75
    • Deep writes check the table name in two stages PutItem reports only the length for a long name with a valid pattern source:75
    • Deep writes check the table name in two stages UpdateItem lists a missing name second, after a bad ReturnConsumedCapacity source:75
    • Deep writes check the table name in two stages UpdateItem lists an empty name as a member error after a bad ReturnConsumedCapacity source:75
    • Deep writes check the table name in two stages UpdateItem drops a short name beside a bad ReturnConsumedCapacity source:75
    • Deep writes check the table name in two stages UpdateItem drops a short name with bad characters beside a bad ReturnConsumedCapacity source:75
    • Deep writes check the table name in two stages UpdateItem drops a 300-character name beside a missing Key source:75
    • Deep writes check the table name in two stages UpdateItem lists the length then the pattern for a short name with bad characters source:75
    • Deep writes check the table name in two stages UpdateItem lists the length then the pattern for a long name with bad characters source:75
    • Deep writes check the table name in two stages DeleteItem lists a missing name after XOR source:75
    • Deep writes check the table name in two stages DeleteItem lists a missing name last, after every bad member and the missing Key source:75
    • Deep writes check the table name in two stages DeleteItem reads a null name as missing and drops a ReturnValues of ALL_NEW beside XOR source:75
    • Deep writes check the table name in two stages DeleteItem reports an empty name alone in the envelope source:75
    • Deep writes check the table name in two stages DeleteItem drops a name with bad characters beside XOR source:75
    • Deep writes check the table name in two stages DeleteItem lists the length then the pattern for a short name with bad characters source:75
    • Deep writes check the table name in two stages DeleteItem reports only the pattern for a long enough name with bad characters source:75
    • Deep writes check the table name in two stages DeleteItem reports the name errors ahead of a ReturnValues of ALL_NEW source:75
    • Deep writes check the table name in two stages DeleteItem keeps the bare ReturnValues sentence for ALL_NEW alone source:75
    • Deep writes count a table name in UTF-16 units PutItem finds two accented letters too short source:75
    • Deep writes count a table name in UTF-16 units PutItem does not find 200 accented letters too long source:75
    • Deep writes count a table name in UTF-16 units PutItem does not find two emoji too short source:75
    • Deep writes count a table name in UTF-16 units UpdateItem finds two accented letters too short source:75
    • Deep writes count a table name in UTF-16 units UpdateItem does not find two emoji too short source:75
    • Deep writes count a table name in UTF-16 units UpdateItem finds 128 emoji too long source:75
    • Deep writes count a table name in UTF-16 units DeleteItem finds two accented letters too short source:75
    • Deep writes count a table name in UTF-16 units DeleteItem does not find two emoji too short source:75
    • Deep writes count a table name in UTF-16 units DeleteItem finds 128 emoji too long source:75
    • Query - ConditionalOperator beside Select reports XOR with two QueryFilter conditions before an unknown Select source:96
    • Query - KeyConditionExpression validation ordering a bad operand written before an undefined value is reported first source:43
    • Query - KeyConditionExpression validation ordering a bad operand in the middle clause is reported ahead of a later undefined value source:49
    • Query - KeyConditionExpression validation ordering a bad operand is reported ahead of a third condition source:55
    • Query - KeyConditionExpression validation ordering a bad operand is reported ahead of a missing table source:60
    • TransactWriteItems - validation ordering reports both unknown enums in one message, ReturnConsumedCapacity first source:99
    • TransactWriteItems - validation ordering refuses a ClientRequestToken over 36 characters source:149
    • TransactWriteItems - validation ordering reports a ClientRequestToken over 36 characters ahead of an unknown ReturnConsumedCapacity source:163
    • TransactWriteItems - validation ordering reports a malformed condition on a later action ahead of a missing table on an earlier one source:51
    • TransactWriteItems - validation ordering reports a malformed condition on the first action ahead of a too deep item on the second source:215
    • TransactWriteItems - validation ordering reports an unused value ahead of a missing table on an earlier action source:51
    • UpdateItem - member errors beside a missing Key joins an empty table name with the missing key source:93
    • UpdateItem - member errors beside a missing Key joins the enums, an empty table name and the missing key in member order source:105
    • UpdateItem - member errors beside a missing Key joins XOR with two Expected conditions to the missing key source:121
    • PartiQL - validation ordering the operand-type check fires ahead of table resolution
    • PartiQL - validation ordering a well-formed statement on the same table reports it missing
    • PartiQL - validation ordering an empty path component fires ahead of table resolution
    • PartiQL - validation ordering a negated sort-key term in an OR filter waits for table resolution
    • PartiQL - validation ordering a number for a partition key, twice waits for table resolution
    • PartiQL - validation ordering a number for a partition key waits for table resolution
    • PartiQL - validation ordering a boolean for a partition key waits for table resolution
    • PartiQL - validation ordering a boolean for a partition key beside two sort keys waits for table resolution
    • PartiQL - validation ordering ORDER BY over two branches on one partition waits for table resolution
    • PartiQL - validation ordering ORDER BY on the sort key over two partitions waits for table resolution
    • PartiQL - validation ordering sort-key ranges that meet waits for table resolution
    • PartiQL - validation ordering an unbounded OR branch beside a sort-key equality waits for table resolution
    • PartiQL - validation ordering an unprojected OR filter on an index waits for table resolution
    • PartiQL - validation ordering a Limit of 0 fires ahead of table resolution
    • PartiQL - validation ordering a Limit of -1 fires ahead of table resolution
    • PartiQL - validation ordering a Limit sent as a string fails deserialisation ahead of table resolution
  • limits Tier 3 68 diverging 5 not attempted
    View these tests in the suite →
    • Expression size limit (4KB) - UpdateExpression rejects an UpdateExpression over the 4096-byte limit source:150
    • Expression size limit (4KB) - ConditionExpression rejects a ConditionExpression over the 4096-byte limit source:181
    • Expression size limit (4KB) - Query FilterExpression rejects a Query FilterExpression over the 4096-byte limit source:224
    • Item size limit by surface - TransactWriteItems an Update one byte over surfaces as a cancellation, with the update wording source:221
    • Item size limit by surface - TransactWriteItems answers the same way for a fresh key and for an existing row source:221
    • Item size limit by surface - UpdateItem does not charge for the key sits below 409,600 at a one-byte key, so the exclusion binds source:451
    • Item size limit by surface - UpdateItem does not charge for the key caps at exactly 409,600 with a 100-byte key value source:451
    • Item size limit by surface - UpdateItem does not charge for the key caps at exactly 409,600 with a 1024-byte key value source:451
    • Item size limit by surface - UpdateItem does not charge for the key buys back the same headroom from the key name as from the key value source:451
    • Item size limit by surface - UpdateItem does not charge for the key buys back a sort key’s own bytes as well source:451
    • Item size limit by surface - UpdateItem charges per action charges a second SET clause exactly 19 bytes source:451
    • Item size limit by surface - UpdateItem charges per action charges a REMOVE alongside a SET exactly 2 bytes source:451
    • Item size limit by surface - UpdateItem charges per action charges the clause, not the value it writes source:451
    • Item size limit by surface - UpdateItem charges per action does not charge for an attribute the statement leaves alone source:451
    • Item size limit by surface - UpdateItem charges per action charges the clause, not the attribute name or its alias source:451
    • Item size limit by surface - UpdateItem through a document path charges a SET through a nested path the same as a plain SET source:666
    • Item size limit by surface - UpdateItem through a document path charges a SET through a list index exactly one byte more source:666
    • Item size limit by surface - a transacted Update does not inherit the exclusion writes what UpdateItem refuses at the same key source:746
    • Item size limit by surface - UpdateItem charges each kind of clause charges a path operand 15 bytes plus its name, not the value it copies source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a nested path operand 14 bytes plus the element for each element source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges list_append 37 bytes plus its operands source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a document value operand at its size, at every use source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges an addition 34 bytes plus its operands, whatever the result source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a subtraction 37 bytes plus its operands source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges if_not_exists 39 bytes plus its operands, whether or not the path exists source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges an ADD 19 bytes plus its path and the value added source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges an ADD to a set only for the members it adds source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a REMOVE one byte plus its path source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a REMOVE through a list index 4 bytes plus its digits source:885
    • Item size limit by surface - UpdateItem charges each kind of clause charges a DELETE one byte plus its path, not the members it removes source:885
    • Item size limit by surface - AttributeUpdates sizes the finished item caps the finished item at exactly 409,600 alone source:1092
    • Item size limit by surface - AttributeUpdates sizes the finished item caps the finished item at exactly 409,600 beside an untouched attribute source:1093
    • Item size limit by surface - UpdateItem checks the charge before the condition refuses an over-limit charge even when the condition would fail source:1124
    • Item size limit by surface - UpdateItem checks the charge before the condition refuses an over-limit charge when the condition passes, and with no condition source:1129
    • Leading underscore in expressions rejects one in a FilterExpression on Query and Scan source:51
    • Leading underscore in expressions rejects one in a ProjectionExpression source:62
    • Leading underscore in expressions rejects one in a KeyConditionExpression, on a table and on an index source:76
    • Leading underscore in expressions rejects one in a ConditionExpression source:103
    • Leading underscore in expressions rejects one in an UpdateExpression source:117
    • Leading underscore in expressions accepts an underscore inside a name without an alias source:215
    • Nesting depth - 32-level document limit rejects a stored attribute nested 32 levels (leaf at level 33) source:99
    • Nesting depth - 32-level document limit accepts a 32-level ExpressionAttributeValue (condition is evaluated) source:158
    • Nesting depth - 32-level document limit rejects a stored attribute nested 61 levels with the same message source:182
    • Nesting depth - 32-level document limit rejects a stored attribute nested 63 levels without the envelope source:193
    • Nesting depth - 32-level document limit rejects a 63-level ExpressionAttributeValue naming its key source:204
    • Nesting depth - TransactWriteItems refuses a ConditionCheck value nested 33 levels before the transaction runs source:469
    • Nesting depth - TransactWriteItems refuses a Put whose condition compares a value nested 33 levels, and writes nothing source:493
    • Nesting depth - TransactWriteItems refuses a ConditionCheck map value nested 61 levels, naming the key source:548
    • Nesting depth - TransactWriteItems refuses a ConditionCheck list value nested 61 levels, naming the key source:548
    • A number's byte cost sizes '1.5' at '3 bytes' source:104
    • A number's byte cost sizes '1.2' at '3 bytes' source:104
    • A number's byte cost sizes '1.200' at '3 bytes' source:104
    • A number's byte cost sizes '1.234' at '4 bytes' source:104
    • A number's byte cost sizes '3.14159' at '5 bytes' source:104
    • A number's byte cost sizes '100.5' at '4 bytes' source:104
    • Number limits - exponents an exponent past a 32-bit integer overflows source:56
    • Number limits - exponents a negative exponent past a 32-bit integer underflows source:60
    • Number limits - exponents an exponent one past a 32-bit integer overflows source:64
    • Number limits - exponents zero with an exponent above the range overflows source:72
    • Number limits - exponents zero with an exponent below the range underflows source:76
    • Number limits - exponents an UpdateExpression value with an exponent past a 32-bit integer overflows source:92
    • Number limits - exponents a ConditionExpression value with an exponent past a 32-bit integer overflows source:105
    • Number limits - exponents a GetItem key with an exponent past a 32-bit integer overflows source:122
    • Number limits - exponents a DeleteItem key with an exponent past a 32-bit integer overflows source:130
    • Number limits - exponents an UpdateItem key with an exponent past a 32-bit integer overflows source:138
    • Number limits - exponents a Query sort-key value with an exponent past a 32-bit integer overflows source:151
    • Number limits - exponents a BatchGetItem key with an exponent past a 32-bit integer overflows source:163
    • Number precision - DynamoDB number limits and edge cases numeric sort key preserves ordering at precision boundaries source:386
    • Item size limit by surface - PartiQL INSERT accepts an item of exactly 409,600 bytes
    • Item size limit by surface - PartiQL INSERT refuses it one byte over, with the put wording
    • Item size limit by surface - PartiQL UPDATE accepts a finished item of exactly 409,600 bytes
    • Item size limit by surface - PartiQL UPDATE refuses it one byte over, with the update wording
    • Item size limit by surface - a PartiQL UPDATE does not inherit the exclusion writes what UpdateItem refuses at the same key
  • multiAttributeKeys Tier 2 12 diverging
    View these tests in the suite →
    • Query - GSI with a multi-attribute key the HASH attribute alone returns the indexed items in key order, without the item missing a key attribute source:103
    • Query - GSI with a multi-attribute key an equality on the first RANGE attribute narrows to it source:107
    • Query - GSI with a multi-attribute key ScanIndexForward=false reverses the order source:111
    • Query - GSI with a multi-attribute key equalities on the first two RANGE attributes source:92
    • Query - GSI with a multi-attribute key equalities on the first three RANGE attributes source:92
    • Query - GSI with a multi-attribute key a range condition on the last attribute named source:92
    • Query - GSI with a multi-attribute key begins_with on the fourth RANGE attribute source:92
    • Query - GSI with a multi-attribute key BETWEEN on the fourth RANGE attribute source:92
    • Query - GSI with a multi-attribute key a range condition on the second RANGE attribute source:92
    • Query - GSI with a multi-attribute key the clauses can be written in any order source:92
    • Query - GSI with a multi-attribute key a page carries the table key and every index key attribute in LastEvaluatedKey source:144
    • Query - GSI with a multi-attribute key skipping the first RANGE attribute is refused source:163
  • query Tier 1 4 diverging
    View these tests in the suite →
    • Query - order of rows tied on an index key returns LSI ties in a fixed order ascending source:80
    • Query - order of rows tied on an index key returns LSI ties in the exact reverse descending source:84
    • Query - order of rows tied on an index key returns GSI ties in a fixed order ascending, different from the LSI source:88
    • Query - order of rows tied on an index key returns GSI ties in the exact reverse descending source:92
  • transactions Tier 2 2 diverging
    View these tests in the suite →
    • TransactWriteItems - index key validation Put with an empty-string index key is a top-level ValidationException source:117
    • TransactWriteItems - index key validation Update setting an empty-string index key is a top-level ValidationException source:136
  • updateItem Tier 1 1 diverging
    View these tests in the suite →
    • UpdateItem - ReturnValues granularity ALL_NEW on a create returns the key and the new attribute source:978
  • updateTable Tier 1 1 diverging
    View these tests in the suite →
    • UpdateTable - basic rejects PROVISIONED to PROVISIONED no-op with same throughput values source:73

Tests that got no answer

The tests ExtendDB (MongoDB)'s latest run got no answer to, by operation, each with the reason the suite recorded. None of them is a divergence: an absent answer is not a different one, and any one of them is enough for a run to be not scored.

  • updateItem Tier 1 1 got no answer
    • UpdateItem - ReturnValues granularity ALL_OLD on an existing item returns the item as it was (a transport failure or 5xx) source:984

What it doesn't attempt

Operations ExtendDB (MongoDB) declines rather than gets wrong, so none of this counts towards its divergence. It is what the gap in its - coverage is made of. Each test here skipped itself because the target's own feature probe said the operation isn't implemented, which is often a deliberate choice rather than a defect.

  • partiql Tier 2 none of it 356 not attempted
    View these tests in the suite →
    • BatchExecuteStatement - PartiQL batch of multiple SELECT statements
    • BatchExecuteStatement - PartiQL batch of INSERT and UPDATE statements
    • BatchExecuteStatement - PartiQL partial failure - one valid and one invalid statement
    • BatchExecuteStatement - PartiQL honours a RETURNING clause on a member statement
    • BatchExecuteStatement - PartiQL honours a RETURNING ALL NEW * clause on a member UPDATE
    • BatchExecuteStatement - PartiQL honours a RETURNING MODIFIED NEW * clause on a member UPDATE (only the changed attr)
    • BatchExecuteStatement - PartiQL omits Item when a member UPDATE produces an empty MODIFIED projection
    • BatchExecuteStatement - PartiQL surfaces an invalid RETURNING variant on a member DELETE as a per-statement error
    • BatchExecuteStatement - PartiQL surfaces a malformed member statement as a per-statement ValidationError without failing the batch
    • BatchExecuteStatement - PartiQL rejects an empty Statements array
    • BatchExecuteStatement - PartiQL ConsistentRead is honoured per member charges a small eventually-consistent read half a unit
    • BatchExecuteStatement - PartiQL ConsistentRead is honoured per member charges exactly twice that when the member asks for consistency
    • BatchExecuteStatement - PartiQL ConsistentRead is honoured per member treats an explicit false the same as omitting it
    • BatchExecuteStatement - PartiQL ConsistentRead is honoured per member rates each member of a mixed batch on its own setting
    • BatchExecuteStatement - PartiQL a batch SELECT must name the table primary key rejects a member that filters on a non-key attribute
    • BatchExecuteStatement - PartiQL a batch SELECT must name the table primary key rejects an index-qualified member naming the index key
    • BatchExecuteStatement - PartiQL a batch SELECT must name the table primary key rejects one naming both the table primary key and the index key
    • BatchExecuteStatement - PartiQL a batch SELECT must name the table primary key rejects a member naming the partition key but not the sort key
    • BatchExecuteStatement - PartiQL a batch SELECT must name the table primary key leaves the rest of the batch running
    • BatchExecuteStatement - PartiQL a failed member echoes its table only if it ran carries TableName on a conditional failure
    • BatchExecuteStatement - PartiQL a failed member echoes its table only if it ran carries TableName on a duplicate insert
    • BatchExecuteStatement - PartiQL a failed member echoes its table only if it ran omits TableName on a member rejected before it ran
    • BatchExecuteStatement - PartiQL ReturnValuesOnConditionCheckFailure on a batch member returns no Item with the option set to ALL_OLD
    • BatchExecuteStatement - PartiQL ReturnValuesOnConditionCheckFailure on a batch member returns no Item with the option set to NONE
    • BatchExecuteStatement - PartiQL ReturnValuesOnConditionCheckFailure on a batch member returns no Item with the option set to undefined
    • BatchExecuteStatement - PartiQL ReturnValuesOnConditionCheckFailure on a batch member does return the item on a TransactWriteItems ConditionCheck
    • ExecuteStatement - comparison on non-scalar types 'SS' matches an equal value
    • ExecuteStatement - comparison on non-scalar types 'SS' does not match a different value
    • ExecuteStatement - comparison on non-scalar types 'SS' answers <> as the complement of =
    • ExecuteStatement - comparison on non-scalar types 'SS' matches a permuted value, because a string set is unordered
    • ExecuteStatement - comparison on non-scalar types 'SS' agrees with the same predicate as a ConditionExpression
    • ExecuteStatement - comparison on non-scalar types 'NS' matches an equal value
    • ExecuteStatement - comparison on non-scalar types 'NS' does not match a different value
    • ExecuteStatement - comparison on non-scalar types 'NS' answers <> as the complement of =
    • ExecuteStatement - comparison on non-scalar types 'NS' matches a permuted value, because a number set is unordered
    • ExecuteStatement - comparison on non-scalar types 'NS' agrees with the same predicate as a ConditionExpression
    • ExecuteStatement - comparison on non-scalar types 'BS' matches an equal value
    • ExecuteStatement - comparison on non-scalar types 'BS' does not match a different value
    • ExecuteStatement - comparison on non-scalar types 'BS' answers <> as the complement of =
    • ExecuteStatement - comparison on non-scalar types 'BS' matches a permuted value, because a binary set is unordered
    • ExecuteStatement - comparison on non-scalar types 'BS' agrees with the same predicate as a ConditionExpression
    • ExecuteStatement - comparison on non-scalar types 'L' matches an equal value
    • ExecuteStatement - comparison on non-scalar types 'L' does not match a different value
    • ExecuteStatement - comparison on non-scalar types 'L' answers <> as the complement of =
    • ExecuteStatement - comparison on non-scalar types 'L' does not match a permuted value, because a list is ordered, so a permutation is a different value
    • ExecuteStatement - comparison on non-scalar types 'L' agrees with the same predicate as a ConditionExpression
    • ExecuteStatement - comparison on non-scalar types 'M' matches an equal value
    • ExecuteStatement - comparison on non-scalar types 'M' does not match a different value
    • ExecuteStatement - comparison on non-scalar types 'M' answers <> as the complement of =
    • ExecuteStatement - comparison on non-scalar types 'M' matches a permuted value, because a map compares by content, not by the order its keys arrived in
    • ExecuteStatement - comparison on non-scalar types 'M' agrees with the same predicate as a ConditionExpression
    • ExecuteStatement - comparison on non-scalar types 'B' matches an equal value
    • ExecuteStatement - comparison on non-scalar types 'B' does not match a different value
    • ExecuteStatement - comparison on non-scalar types 'B' answers <> as the complement of =
    • ExecuteStatement - comparison on non-scalar types 'B' agrees with the same predicate as a ConditionExpression
    • ExecuteStatement - comparison on non-scalar types 'NULL' matches an equal value
    • ExecuteStatement - comparison on non-scalar types 'NULL' does not match a different value
    • ExecuteStatement - comparison on non-scalar types 'NULL' answers <> as the complement of =
    • ExecuteStatement - comparison on non-scalar types 'NULL' agrees with the same predicate as a ConditionExpression
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering rejects < against BOOL
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering rejects < against NULL
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering rejects < against L
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering rejects < against M
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering rejects < against SS
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering rejects < against NS
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering rejects < against BS
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering names the operator < as written
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering names the operator <= as written
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering names the operator > as written
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering names the operator >= as written
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering names BETWEEN as written too
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering accepts = and <> against BOOL
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering accepts = and <> against NULL
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering accepts = and <> against L
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering accepts = and <> against M
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering accepts = and <> against SS
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering accepts = and <> against NS
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering accepts = and <> against BS
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering accepts an ordering comparison between S and N
    • ExecuteStatement - comparison on non-scalar types ordering operators reject an operand type with no ordering orders binary by its bytes
    • ExecuteStatement - comparison on non-scalar types a write conditioned on a non-scalar predicate fires when the predicate holds
    • ExecuteStatement - comparison on non-scalar types a write conditioned on a non-scalar predicate raises ConditionalCheckFailed and leaves the item when it does not
    • ExecuteStatement - PartiQL INSERTs a new item
    • ExecuteStatement - PartiQL SELECTs an item by primary key
    • ExecuteStatement - PartiQL SELECTs with WHERE clause using comparison
    • ExecuteStatement - PartiQL UPDATEs an existing item
    • ExecuteStatement - PartiQL DELETEs an item
    • ExecuteStatement - PartiQL rejects INSERT on an existing item (INSERT is not upsert)
    • ExecuteStatement - PartiQL INSERT succeeds after DELETE of same key
    • ExecuteStatement - PartiQL SELECT returns empty results for non-matching WHERE
    • ExecuteStatement - PartiQL parameterized INSERT with ? placeholders
    • ExecuteStatement - PartiQL parameterized SELECT with ? placeholder
    • ExecuteStatement - PartiQL SELECT with nested map path
    • ExecuteStatement - PartiQL SELECT with specific attributes
    • ExecuteStatement - PartiQL SELECT with begins_with in WHERE clause
    • ExecuteStatement - PartiQL PartiQL UPDATE with SET on attribute
    • ExecuteStatement - PartiQL PartiQL UPDATE with REMOVE
    • ExecuteStatement - PartiQL returns a populated ConsumedCapacity block when requested
    • ExecuteStatement - PartiQL evaluates negated predicates (NOT begins_with, IS NOT MISSING)
    • ExecuteStatement - PartiQL DELETE with a false non-key predicate fails ConditionalCheckFailed and leaves the item
    • ExecuteStatement - PartiQL DELETE with a true non-key predicate removes the item
    • ExecuteStatement - PartiQL UPDATE with a false non-key predicate fails ConditionalCheckFailed and leaves the item
    • ExecuteStatement - PartiQL UPDATE with a true non-key predicate mutates the item
    • ExecuteStatement - PartiQL DELETE with a false NOT begins_with predicate fails ConditionalCheckFailed
    • ExecuteStatement - PartiQL DELETE with a true NOT begins_with predicate removes the item
    • ExecuteStatement - PartiQL rejects a write WHERE clause that omits the primary key
    • ExecuteStatement - PartiQL DELETE on a missing key with a non-key predicate is a silent no-op
    • ExecuteStatement - PartiQL DELETE RETURNING ALL OLD * returns the deleted item
    • ExecuteStatement - PartiQL DELETE RETURNING ALL OLD * on a missing item returns an empty Items list
    • ExecuteStatement - PartiQL DELETE rejects RETURNING MODIFIED OLD * (only ALL OLD * is valid on DELETE)
    • ExecuteStatement - PartiQL DELETE rejects RETURNING MODIFIED NEW * (only ALL OLD * is valid on DELETE)
    • ExecuteStatement - PartiQL DELETE rejects RETURNING ALL NEW * with a 400, not a 500
    • ExecuteStatement - PartiQL UPDATE RETURNING ALL OLD * returns the full prior item
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * returns only the changed attribute (old value, no key)
    • ExecuteStatement - PartiQL UPDATE RETURNING ALL NEW * returns the full new item
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * returns only the changed attribute (new value, no key)
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * over a nested path returns only the changed leaf
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * over a nested path returns only the changed leaf at its old value
    • ExecuteStatement - PartiQL UPDATE REMOVE RETURNING MODIFIED OLD * returns the removed attribute at its old value
    • ExecuteStatement - PartiQL UPDATE REMOVE RETURNING MODIFIED NEW * returns an empty Items list
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * on a newly-set attribute returns an empty Items list
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * on a newly-set attribute returns the new value
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * on a list index returns only the changed element
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * on a list index returns only the prior element
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * on a non-zero list index returns only the changed element
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * on a non-zero list index returns the prior element
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * over multiple list indices returns a dense pack of the changed elements
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * over multiple list indices returns the prior elements densely
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * packs changed indices in ascending index order, not statement order
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * packs changed indices in ascending index order, not statement order
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * on an out-of-range list index (append) returns an empty Items list
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * on an out-of-range list index (append) returns an empty Items list
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * appending at exactly the list length returns the appended element
    • ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * appending at exactly the list length returns an empty Items list
    • ExecuteStatement - PartiQL UPDATE REMOVE RETURNING MODIFIED OLD * on a list index returns the removed element at its old value
    • ExecuteStatement - PartiQL UPDATE REMOVE RETURNING MODIFIED NEW * on a list index returns the shifted element, not an empty list
    • ExecuteStatement - PartiQL UPDATE REMOVE RETURNING MODIFIED NEW * on the last list index returns an empty Items list
    • ExecuteStatement - PartiQL UPDATE REMOVE RETURNING MODIFIED OLD * on the last list index returns the removed element
    • ExecuteStatement - PartiQL UPDATE SET on a list index of an absent attribute is rejected, not auto-created
    • ExecuteStatement - PartiQL UPDATE on a non-existent key fails ConditionalCheckFailed (PartiQL UPDATE is not an upsert)
    • ExecuteStatement - PartiQL Limit a Limit at or past the 32-bit range returns the whole partition on one page
    • ExecuteStatement - PartiQL Limit a Limit near the 64-bit range returns a whole set of keys on one page
    • ExecuteStatement - PartiQL Limit a Limit written with an exponent or past 64 bits returns the whole partition on one page
    • ExecuteStatement - PartiQL Limit a Limit of 1.0 reads as 1, one row a page
    • ExecuteStatement - PartiQL Limit a Limit of 1.5 reads as 1, one row a page
    • ExecuteStatement - PartiQL rejects a statement with syntax error
    • ExecuteStatement - PartiQL rejects a reference to a non-existent table
    • ExecuteTransaction - PartiQL transactional INSERT and UPDATE both succeed atomically
    • ExecuteTransaction - PartiQL transaction rolls back on duplicate key INSERT
    • ExecuteTransaction - PartiQL multiple INSERTs in one transaction
    • ExecuteTransaction - PartiQL idempotent replay under the same ClientRequestToken does not double-apply
    • ExecuteTransaction - PartiQL rejects a RETURNING clause inside a transaction statement
    • ExecuteTransaction - PartiQL rejects empty TransactStatements
    • PartiQL - FROM-first UPDATE FROM ... WHERE ... SET updates the item
    • PartiQL - FROM-first UPDATE FROM ... WHERE ... REMOVE removes the attribute
    • PartiQL - FROM-first UPDATE SET and REMOVE can follow each other
    • PartiQL - FROM-first UPDATE RETURNING ALL NEW * returns the updated item
    • PartiQL - FROM-first UPDATE the keywords are case-insensitive
    • PartiQL - FROM-first UPDATE takes parameters
    • PartiQL - FROM-first UPDATE a further condition in the WHERE that holds lets the update through
    • PartiQL - FROM-first UPDATE a further condition in the WHERE that fails stops the update
    • PartiQL - FROM-first UPDATE a key that matches no item fails its condition and creates nothing
    • PartiQL - FROM-first UPDATE ExecuteTransaction runs it
    • PartiQL - FROM-first UPDATE BatchExecuteStatement runs it
    • PartiQL - grammar an exponent literal in WHERE matches the number it denotes
    • PartiQL - grammar an upper-case E, an explicit sign and a shifted mantissa all match the same number
    • PartiQL - grammar an exponent literal in an INSERT stores the number it denotes
    • PartiQL - grammar a number with no leading digit matches in WHERE
    • PartiQL - grammar a negative number with no leading digit matches in WHERE
    • PartiQL - grammar a number with no leading digit in an INSERT stores the number it denotes
    • PartiQL - grammar an exponent that does not fit a 32-bit integer is refused
    • PartiQL - grammar a line comment after the statement is ignored
    • PartiQL - grammar a line comment between FROM and WHERE leaves the WHERE clause in force
    • PartiQL - grammar a line comment before the statement is ignored
    • PartiQL - grammar a block comment between clauses is ignored
    • PartiQL - grammar a block comment after the statement is ignored
    • PartiQL - grammar a hash comment is refused
    • PartiQL - grammar ORDER BY the sort key DESC returns the rows in descending order
    • PartiQL - grammar ORDER BY the sort key ASC returns the rows in ascending order
    • PartiQL - grammar ORDER BY the sort key DESC is accepted on an OR filter inside one partition
    • PartiQL - grammar ORDER BY the sort key is accepted on an OR filter inside one partition
    • PartiQL - grammar a number key written twice in two spellings of the same value reads that key
    • PartiQL - grammar a number key given as two equal parameters reads that key
    • PartiQL - grammar a string key written twice as the same literal reads the partition
    • PartiQL - grammar an INSERT with a token left over is refused and writes nothing
    • PartiQL - grammar a SELECT with a table alias is refused rather than read without its WHERE clause
    • PartiQL - grammar a DELETE with a table alias is refused and deletes nothing
    • PartiQL - grammar a DELETE with ORDER BY is refused and deletes nothing
    • ExecuteStatement - index qualifier membership a qualified SELECT omits an item the index does not hold
    • ExecuteStatement - index qualifier projection follows the index, not the item a KEYS_ONLY GSI returns the index key and the table key and nothing else
    • ExecuteStatement - index qualifier projection follows the index, not the item an INCLUDE GSI adds the named attribute and no others
    • ExecuteStatement - index qualifier projection follows the index, not the item a KEYS_ONLY LSI returns the index key and the table key and nothing else
    • ExecuteStatement - index qualifier projection follows the index, not the item SELECT * against a non-ALL index does not reach back
    • ExecuteStatement - index qualifier the reach-back splits by index kind an LSI serves an unprojected attribute from the base table
    • ExecuteStatement - index qualifier the reach-back splits by index kind a GSI rejects an unprojected attribute rather than reaching back
    • ExecuteStatement - index qualifier the reach-back splits by index kind naming only projected attributes on an LSI charges no table arm
    • ExecuteStatement - index qualifier the reach-back splits by index kind a filtered reach-back is charged on rows walked, not rows kept
    • ExecuteStatement - index qualifier the reach-back splits by index kind a bounded reach-back walks fewer rows and is charged less
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects a keyed GSI read filtering on an unprojected attribute
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects the LSI mirror, so the rule is not about index kind
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts the same GSI filter unkeyed, matching nothing
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts the same LSI filter unkeyed, matching nothing
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts two unprojected filters with no index key
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts a keyed read filtering on an attribute the index does project
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects a keyed read with IS MISSING on an unprojected attribute
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects a keyed read with IS NOT MISSING on an unprojected attribute
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects a keyed read with begins_with on an unprojected attribute
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts the same predicate on a projected attribute
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects a keyed read with a negated filter on an unprojected attribute
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition matches every index row when the negated filter names an absent attribute
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition counts IN on the index partition key as keyed
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts an unprojected filter inside an OR branch
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects an OR of unprojected filters beside the index partition key
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects the same OR beside a multi-value IN on the index partition key
    • ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition counts BETWEEN on the index sort key as keyed
    • ExecuteStatement - index qualifier pagination across a qualified read mints a token when a bounded read leaves rows behind
    • ExecuteStatement - index qualifier pagination across a qualified read rejects a token minted against one index and replayed against another
    • ExecuteStatement - index qualifier a set of LSI keys holds the token past a missing key written after the found key
    • ExecuteStatement - index qualifier a set of LSI keys holds the token past a missing key written before the found key
    • ExecuteStatement - index qualifier a set of LSI keys charges a missing key beside a found one under ConsistentRead
    • ExecuteStatement - index qualifier a set of LSI keys charges per key, not per row, for two found keys over three rows
    • ExecuteStatement - index qualifier a set of LSI keys returns every row across pages when two rows share a key
    • ExecuteStatement - index qualifier write statements reject the qualifier, and not all the same way rejects an INSERT carrying a qualifier at parse position
    • ExecuteStatement - index qualifier write statements reject the qualifier, and not all the same way rejects an INSERT whose qualifier names no index with the same message
    • ExecuteStatement - index qualifier write statements reject the qualifier, and not all the same way rejects an UPDATE carrying a qualifier semantically
    • ExecuteStatement - index qualifier write statements reject the qualifier, and not all the same way rejects a DELETE carrying a qualifier semantically
    • ExecuteStatement - index qualifier write statements reject the qualifier, and not all the same way leaves the rows untouched after the rejected writes
    • ExecuteStatement - index qualifier a transaction refuses an index-qualified read rejects it outright, not as a cancellation
    • ExecuteStatement - index qualifier a transaction refuses an index-qualified read accepts the same read unqualified
    • ExecuteStatement - index qualifier capacity lands on the index arm a keyed GSI read charges the index and a zero table arm
    • ExecuteStatement - index qualifier capacity lands on the index arm a keyed LSI read charges the index and a zero table arm
    • ExecuteStatement - index qualifier capacity lands on the index arm ConsistentRead doubles the LSI arm
    • ExecuteStatement - index qualifier capacity lands on the index arm ConsistentRead doubles both arms of a reach-back
    • ExecuteStatement - index qualifier capacity lands on the index arm rejects ConsistentRead against a GSI qualifier
    • ExecuteStatement - order of rows tied on an index key returns LSI ties in the order a Query of the index does
    • ExecuteStatement - order of rows tied on an index key returns two rows sharing an LSI key in a fixed order, not sort-key order
    • ExecuteStatement - order of rows tied on an index key reverses that order under ORDER BY on the tied key descending
    • PartiQL - GSI with a multi-attribute key a SELECT on a GSI with two HASH and two RANGE attributes is refused
    • PartiQL - GSI with a multi-attribute key a SELECT with ORDER BY on that index is refused too
    • PartiQL - GSI with a multi-attribute key a SELECT on a GSI with two HASH attributes and one RANGE is refused
    • PartiQL - GSI with a multi-attribute key the same table's base table, single-attribute GSI and LSI still read
    • PartiQL - GSI with a multi-attribute key base table SELECT, INSERT, UPDATE and DELETE run on a table whose GSI is multi-attribute
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys under Limit 1 take two pages, the second with no token, written as one OR of sort-key equalities
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys under Limit 1 take two pages, the second with no token, written as two branches that each name the partition key
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys under Limit 1 take two pages, the second with no token, written as parameters
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys under Limit 2 come back on one page with no token
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys under Limit 3 come back on one page with no token
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key three keys under Limit 2 take two pages, the second with no token
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys read descending return the higher key first and end on the lower
    • PartiQL - OR reads in one partition: paging a set of sort keys ends on its last key two keys with a row between them read descending skip that row
    • PartiQL - OR reads in one partition: paging number sort keys keys 1.5 and 10 under Limit 1 take two pages, the second with no token
    • PartiQL - OR reads in one partition: paging number sort keys keys -1 and 1.5 under Limit 1 take two pages, the second with no token
    • PartiQL - OR reads in one partition: paging a missing key a missing last key keeps the token for an empty half-unit page, ascending
    • PartiQL - OR reads in one partition: paging a missing key a missing last key keeps the token for an empty half-unit page, descending
    • PartiQL - OR reads in one partition: paging a missing key a missing first key gives one page with no token, charged for both keys, ascending
    • PartiQL - OR reads in one partition: paging a missing key a missing first key gives one page with no token, charged for both keys, descending
    • PartiQL - OR reads in one partition: paging a missing key a missing key between two found ones is charged on the second page, ascending
    • PartiQL - OR reads in one partition: paging a missing key a missing key between two found ones is charged on the second page, descending
    • PartiQL - OR reads in one partition: paging a single key a full key under Limit 1 gives one page with no token
    • PartiQL - OR reads in one partition: paging a single key a full key with a filter under Limit 1 gives one page with no token
    • PartiQL - OR reads in one partition: paging a single key a single key read descending under Limit 1 gives one page with no token
    • PartiQL - OR reads in one partition: paging a single key a missing single key under Limit 1 gives one page with no token
    • PartiQL - OR reads in one partition: paging a sort-key IN two found keys under Limit 1 take two pages, the second with no token
    • PartiQL - OR reads in one partition: paging a sort-key IN a missing last key keeps the token for an empty half-unit page
    • PartiQL - OR reads in one partition: paging a sort-key IN read descending returns the higher key first
    • PartiQL - OR reads in one partition: paging ranges with closed bounds BETWEEN under Limit 1 ends on the bound with no trailing empty page
    • PartiQL - OR reads in one partition: paging ranges with closed bounds <= under Limit 2 ends on the bound with no trailing empty page
    • PartiQL - OR reads in one partition: paging ranges with closed bounds BETWEEN over three rows under Limit 3 ends on the bound with no trailing empty page
    • PartiQL - OR reads in one partition: paging ranges with closed bounds >= read descending under Limit 1 ends on the bound with no trailing empty page
    • PartiQL - OR reads in one partition: paging ranges with closed bounds a union of two closed ranges under Limit 1 ends on the bound with no trailing empty page
    • PartiQL - OR reads in one partition: paging ranges with closed bounds an empty branch the read has not reached keeps the token for an empty page
    • PartiQL - OR reads in one partition: paging reads whose last page varies two open ranges under Limit 1 returns exactly its rows across the walk
    • PartiQL - OR reads in one partition: paging reads whose last page varies an equality and an open range under Limit 1 returns exactly its rows across the walk
    • PartiQL - OR reads in one partition: paging reads whose last page varies an OR filter on a non-key attribute under Limit 2 returns exactly its rows across the walk
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead two found keys cost 2
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead three found keys cost 3
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead the whole three-row partition costs 1
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead a missing key beside a found one costs 2
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead a missing key repeated within one branch beside a found one costs 2
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead a union of two ranges, one of them empty, costs 2
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead a union of two ranges that each find a row costs 2
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead a key beside a range costs 2
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead an empty begins_with branch beside a found one costs 2
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead an empty BETWEEN branch beside a found one costs 2
    • PartiQL - read capacity of OR and IN on the sort key ConsistentRead an empty range branch read descending costs 2
    • PartiQL - read capacity of OR and IN on the sort key eventually consistent two found keys cost 1
    • PartiQL - read capacity of OR and IN on the sort key eventually consistent two missing keys cost 1
    • PartiQL - read capacity of OR and IN on the sort key eventually consistent three missing keys and one found cost 2
    • PartiQL - read capacity of OR and IN on the sort key IN costs what its OR costs two keys cost 2 under ConsistentRead
    • PartiQL - read capacity of OR and IN on the sort key IN costs what its OR costs two keys cost 1 eventually consistent
    • PartiQL - read capacity of OR and IN on the sort key IN costs what its OR costs three keys cost 3 under ConsistentRead
    • PartiQL - read capacity of OR and IN on the sort key IN costs what its OR costs a missing key and a found one cost 2 under ConsistentRead
    • PartiQL - read capacity of OR and IN on the sort key two sort keys beside a wide filter nine non-key OR pairs that no row passes cost 1 eventually consistent
    • PartiQL - read capacity of OR and IN on the sort key two sort keys beside a wide filter eight IS MISSING OR pairs that every row passes cost 2 under ConsistentRead
    • PartiQL - read capacity of OR and IN on the sort key 2 positive OR pairs naming the sort key are accepted and return nothing
    • PartiQL - read capacity of OR and IN on the sort key 9 positive OR pairs naming the sort key are accepted and return nothing
    • PartiQL - read capacity of a partition key that cannot be a key pk = true beside one closed range finds nothing for 2, or 4 consistently
    • PartiQL - read capacity of a partition key that cannot be a key pk = true beside two closed ranges finds nothing for 2, or 4 consistently
    • PartiQL - read capacity of a partition key that cannot be a key pk = true beside three closed ranges finds nothing for 2, or 4 consistently
    • PartiQL - read capacity of a partition key that cannot be a key pk = 1 on a string key beside one closed range finds nothing for 2, or 4 consistently
    • PartiQL - read capacity of a partition key that cannot be a key pk = 1 on a string key beside two closed ranges finds nothing for 2, or 4 consistently
    • PartiQL - read capacity of a partition key that cannot be a key pk = 1 on a string key beside three closed ranges finds nothing for 2, or 4 consistently
    • PartiQL - set_add and set_delete set_add adds members to a string set
    • PartiQL - set_add and set_delete set_add adds members to a number set
    • PartiQL - set_add and set_delete set_add takes the set to add as a parameter
    • PartiQL - set_add and set_delete set_add of a member already in the set changes nothing
    • PartiQL - set_add and set_delete set_add to a missing attribute creates the set
    • PartiQL - set_add and set_delete the function name is case-insensitive
    • PartiQL - set_add and set_delete two SET clauses can each call set_add
    • PartiQL - set_add and set_delete RETURNING ALL NEW * returns the set after the addition
    • PartiQL - set_add and set_delete set_add on a missing item fails its condition and creates nothing
    • PartiQL - set_add and set_delete set_delete removes a member
    • PartiQL - set_add and set_delete set_delete removes a member from a number set
    • PartiQL - set_add and set_delete removing every member removes the attribute
    • PartiQL - set_add and set_delete removing a member that is not there changes nothing
    • PartiQL - set_add and set_delete set_delete on a missing attribute leaves it missing
    • PartiQL - set_add and set_delete ExecuteTransaction runs set_add
    • PartiQL - set_add and set_delete BatchExecuteStatement runs set_add
    • PartiQL - functions and IS in a WHERE clause attribute_exists keeps an item that has the attribute
    • PartiQL - functions and IS in a WHERE clause attribute_exists drops an item without the attribute
    • PartiQL - functions and IS in a WHERE clause attribute_not_exists keeps an item without the attribute
    • PartiQL - functions and IS in a WHERE clause attribute_not_exists drops an item that has the attribute
    • PartiQL - functions and IS in a WHERE clause NOT attribute_exists keeps an item without the attribute
    • PartiQL - functions and IS in a WHERE clause the function name is case-insensitive
    • PartiQL - functions and IS in a WHERE clause works inside OR and parentheses
    • PartiQL - functions and IS in a WHERE clause can be compared with true
    • PartiQL - functions and IS in a WHERE clause takes a quoted attribute name
    • PartiQL - functions and IS in a WHERE clause a nested path that is present is true
    • PartiQL - functions and IS in a WHERE clause a nested path that is absent is false
    • PartiQL - functions and IS in a WHERE clause filters a SELECT with no key condition
    • PartiQL - functions and IS in a WHERE clause size() compares the length of a string
    • PartiQL - functions and IS in a WHERE clause attribute_type() tests the type of an attribute
    • PartiQL - functions and IS in a WHERE clause IS NULL runs as a filter
    • PartiQL - functions and IS in a WHERE clause IS NOT NULL runs as a filter
    • PartiQL - functions and IS in a WHERE clause IS with a type name runs as a filter
    • PartiQL - functions and IS in a WHERE clause an UPDATE whose attribute_exists holds is applied
    • PartiQL - functions and IS in a WHERE clause an UPDATE whose attribute_exists is false fails its condition and changes nothing
    • PartiQL - functions and IS in a WHERE clause an UPDATE guarded by attribute_not_exists sets the attribute once
    • PartiQL - functions and IS in a WHERE clause a DELETE whose attribute_exists is false fails its condition and keeps the item
    • PartiQL - functions and IS in a WHERE clause a DELETE whose attribute_not_exists holds removes the item
    • PartiQL - functions and IS in a WHERE clause an UPDATE of a missing item guarded by attribute_not_exists(pk) fails and creates nothing
    • PartiQL - functions and IS in a WHERE clause an UPDATE in ExecuteTransaction takes attribute_exists as its condition
    • PartiQL - OR branches with a negated sort-key condition a branch with NOT sk = ... beside an equality branch runs
    • PartiQL - OR branches with a negated sort-key condition a branch with sk <> ... beside an equality branch runs
    • PartiQL - OR branches with a negated sort-key condition a branch with NOT begins_with beside an equality branch runs
    • PartiQL - OR branches with a negated sort-key condition a branch with NOT sk IN beside an equality branch runs
    • PartiQL - OR branches with a negated sort-key condition a branch with NOT sk > ... beside an equality branch runs
    • PartiQL - OR branches with a negated sort-key condition a branch with NOT (sk = ...) beside an equality branch runs
    • PartiQL - OR branches with a negated sort-key condition a bare partition branch beside one with a negated sort key runs
    • PartiQL - responses to writes an INSERT returns an empty Items list
    • PartiQL - responses to writes an UPDATE returns an empty Items list
    • PartiQL - responses to writes a DELETE that removes an item returns an empty Items list
    • PartiQL - responses to writes a DELETE that finds no item returns an empty Items list
    • PartiQL - responses to writes a transaction of updates returns an empty Responses list
    • PartiQL - responses to writes a transaction of an INSERT and a DELETE returns an empty Responses list
    • PartiQL - responses to writes a transaction of writes asked for its capacity returns it beside an empty Responses list
  • vectorSearch Tier 2 none of it 40 not attempted
    View these tests in the suite →
    • SearchVectors - ConsumedCapacity shape reports VectorSearchRequestBytes with no classic capacity fields
    • SearchVectors - ConsumedCapacity shape reports the same shape under INDEXES as under TOTAL
    • SearchVectors - ConsumedCapacity shape reports nothing under NONE
    • PutItem - vector write capacity shape INDEXES adds a per-index VectorWriteRequestBytes map beside the classic fields
    • PutItem - vector write capacity shape TOTAL folds nothing in: no vector fields at all
    • PutItem - vector write capacity shape a write not touching the vector attribute reports no vector write
    • PutItem - vector write capacity shape an identical overwrite reports no vector write: replication is delta-based
    • PutItem - a vector index is charged on the change to its stored view charges the index that projects the changed attribute, and not the one that does not
    • PutItem - a vector index is charged on the change to its stored view charges neither when the write changes nothing either index holds
    • PutItem - VectorWriteRequestBytes reports the 1024 floor for an entry below it on every term
    • PutItem - VectorWriteRequestBytes applies the floor per index, not per write
    • PutItem - VectorWriteRequestBytes charges four bytes per dimension
    • PutItem - VectorWriteRequestBytes charges the vector attribute’s name by its own length
    • PutItem - VectorWriteRequestBytes charges a projected non-vector attribute its own item size
    • PutItem - a vector attribute is billed at four bytes per dimension bills a three-dimension vector at 12 bytes, whatever numbers it holds
    • PutItem - a vector attribute is billed at four bytes per dimension bills a six-dimension vector at 24 bytes, whatever numbers it holds
    • GetItem and the 400KB gate - how a vector is sized charges a read for the vector’s billed size, not the numbers it holds
    • GetItem and the 400KB gate - how a vector is sized holds the item to 400KB with the vector sized by its numbers
    • CreateTable - vector index lifecycle walks CREATING to ACTIVE and describes the index faithfully
    • CreateTable - vector index lifecycle round-trips a SearchSchema of HASH and INLINE_FILTER elements
    • CreateTable - vector index lifecycle accepts the 4096-dimension boundary
    • SearchVectors - index readiness after CreateTable rejects retryably between ACTIVE and the first served search
    • PartiQL - vector indexes are out of reach rejects a PartiQL read of a vector index
    • PartiQL - vector indexes are out of reach reads the vector attribute off the base table like any other item
    • SearchVectors - deterministic search behaviour COSINE: identical vector scores 0, opposite scores 2, lower is closer
    • SearchVectors - deterministic search behaviour EUCLIDEAN: identical vector scores 0, straight-line distance otherwise
    • SearchVectors - deterministic search behaviour DOT_PRODUCT: higher is closer and scores can be negative
    • SearchVectors - deterministic search behaviour returns the identical vector as the top match
    • SearchVectors - deterministic search behaviour omits the vector attribute by default and returns it when projected
    • SearchVectors - deterministic search behaviour caps results at the item count with no pagination surface
    • SearchVectors - deterministic search behaviour stores full precision on the base table and f32 in the index
    • UpdateTable - vector index lifecycle adds an index that backfills like a GSI, enforces one online action, then deletes it
    • UpdateTable - vector index lifecycle refuses to delete the table while a vector index is still being created
    • UpdateTable - vector index lifecycle reports UPDATING with Backfilling false while allocating, and takes a cancel only once backfilling starts
    • CreateTable - vector index request validation rejects Dimensions of 0 at the request model layer
    • CreateTable - vector index request validation rejects an index name shorter than 3 characters
    • SearchVectors - request validation rejects TopK of 0 at the request model layer
    • SearchVectors - request validation rejects a search against an index the table does not have
    • PutItem - vector index write validation accepts a write missing the HASH attribute but leaves it unreachable through that index
    • PutItem - vector index write validation removes an item from the index when its vector attribute is removed
  • contributorInsights Tier 2 none of it 2 not attempted
    View these tests in the suite →
    • Contributor insights - enable/describe/list reports DISABLED by default
    • Contributor insights - enable/describe/list enabling transitions the status and lists the table
  • export Tier 2 none of it 2 not attempted
    View these tests in the suite →
    • Export and import - S3 ExportTableToPointInTime initiates an export and reports it
    • Export and import - S3 ImportTable ingests S3 data into a new table
  • resourcePolicy Tier 2 none of it 2 not attempted
    View these tests in the suite →
    • Resource policies - Put/Get/Delete GetResourcePolicy on a table with no policy throws PolicyNotFoundException
    • Resource policies - Put/Get/Delete Put then Get round-trips the policy, and Delete removes it
  • kinesis Tier 2 none of it 1 not attempted
    View these tests in the suite →
    • Kinesis streaming destination enables a streaming destination and reports it via Describe

Run history

Every percentage here is divergence, per tier and over the whole suite, so lower is better in each column. Coverage is the exception it is named as.

Run Gradecurrent criteria Divergence Movement

Suite on

ca-central-1 joins eu-west-2 on the five Scan rows. It gave the new wording on the 2026-11-07 and 2026-11-14 sweeps and on the three runs on 2026-11-13, which leaves me-central-1 the only region recorded on the old wording. On the 2026-11-14 sweep eu-north-1 stored UpdateItem writes that the statement-sized rule refuses, which it had not done before. Three runs later that day had it answering both ways, so the item-size rows stay as they are.

Ten regions join eu-west-2 on the five Scan rows: ap-northeast-1, ap-south-2, ap-southeast-6, ap-southeast-7, eu-central-2, eu-south-1, eu-south-2, eu-west-1, us-east-2 and us-west-2. Each gave the new wording on the 2026-11-07 sweep and at least one sweep before it, and on three runs against every region on 2026-11-13, which leaves ca-central-1 and me-central-1 on the old wording. ca-central-1 gave the new wording on the 2026-11-07 sweep and on all three runs, but the old wording on the two sweeps before, so it keeps its recorded answer until a second sweep agrees. eu-north-1 gave the old wording on one of the three runs, so it answers Scan both ways for now and keeps its recorded answer, the new wording. The BatchGetItem row doesn't change: me-central-1 gave both answers to an empty RequestItems across the same runs.

eu-west-2 now accepts a 32-level ExpressionAttributeValue in an UpdateItem condition, so the test that pinned its refusal now pins acceptance, and is renamed to say so. It asserts the ConditionalCheckFailedException a false condition gives, the same proof the 31-level test uses. The 2026-11-14 sweep found 19 regions accepting a value they had refused the week before, and by the last of three runs that day 23 did. ap-east-1, ap-southeast-2, ca-west-1, eu-south-2, eu-west-3, mx-central-1, us-east-1, us-west-1 and us-west-2 still refuse it, and me-central-1, which had accepted it until then, now refuses it too. The registry records those ten on that side. The same regions moved together on UpdateItem's ReturnValues error, which now lists UPDATED_NEW where it listed UPDATE_NEW. That test accepts both, and its row now pins the new wording. A stored item is still capped at 32 levels everywhere, and a 63-level value is still refused.

The wait for an index added by UpdateTable to become ACTIVE is now 2 minutes on any emulator, down from 40. Real DynamoDB keeps 40 minutes. The slowest passing index test on any emulator in the published results takes about 31 seconds, against about 25 minutes on real DynamoDB, so the shorter wait only shortens runs where an index never completes. An expired wait is recorded as no answer either way, never as a failure, so no score can change.

PartiQL reads whose OR branches stay in one partition now have paging and capacity tests. Under Limit, a set of sort keys ends on its last key, a missing last key keeps the token for one empty half-unit page, and a branch the read hasn't reached holds the token. Each shape pinned page by page gave the same pages on every walk in eu-west-2 and us-east-1 between 2026-11-03 and 2026-11-05. Page endings that DynamoDB answers at random, such as a page ending inside an open range, are checked only for the keys they return. Each branch costs a unit under ConsistentRead even when it finds nothing, a sort-key IN costs and pages exactly as the equivalent OR does, and a partition key that can't be a key reads the whole table, so beside sort-key ranges it costs what that read does: 2.0, or 4.0 consistent, on the small on-demand table the test uses.

Items tied on an index key come back in a fixed order that isn't the table's sort-key order, and descending is its exact reverse. The order was the same in nine fresh tables across two regions and two AWS accounts, whatever order the items were written in, so Query on an LSI and a GSI, and PartiQL on an LSI, now pin it.

The PartiQL refusals these reads run into are pinned word for word: a negated sort key inside an OR filter, a partition key given the wrong type or a boolean, ORDER BY over branches that each name the partition key, a KEYS_ONLY index asked to filter on an attribute it doesn't project, and ExecuteStatement Limit values of 0, -1 and a string. What DynamoDB accepts is pinned beside them: ORDER BY on an OR in one partition, the same key written twice, and Limit values past 2^31, past 2^64 and written with an exponent or a fraction.

An attribute name starting with an underscore is a syntax error in every expression type unless it goes through ExpressionAttributeNames, including key conditions. An UpdateItem that creates its item returns no Attributes under ALL_OLD or UPDATED_OLD.

Deep PutItem, UpdateItem and DeleteItem requests, read by the older validation layer, now have their joined errors pinned: every bad member, in each operation's own order, under the N validation errors detected envelope even when only one member is wrong.

A table name's length is counted in UTF-16 units on deep writes and on CreateTable, DescribeTable, DeleteTable and UpdateTable, and in characters on shallow item operations, ListTables' start name and index names. So two emoji are long enough for CreateTable and too short for PutItem. Deep writes also check the name in two stages: a missing or empty name is listed among the member errors, while length and pattern errors only show when nothing else is wrong.

Fourteen new rows in registry/splits.json record where me-central-1, and eu-north-1 on Scan, gave the older validation layer's answer to the shallow table-name and leading-underscore cases on 2026-11-05. The other regions agree with eu-west-2. The answers from all 33 regions on 2026-11-05 are in captures/2026-11-05-shallow-validation-rollout.json. On three later runs on 2026-11-13, me-central-1 gave eu-west-2's answer to the twelve cases that aren't Scan (once cut short, on UpdateItem) and eu-north-1 gave it on Scan, so the rows keep the 2026-11-05 answers until a sweep has run the tests. Those runs are in captures/2026-11-13-shallow-validation-follow-up.json.

Four more PartiQL index-qualifier answers are pinned. An unknown index read with ConsistentRead is reported as an unknown index, not as a consistent read on a GSI. Selecting an attribute a GSI doesn't project is refused on an unkeyed scan as well as on a keyed read. With two such attributes the refusal lists them in the same order whichever way round the statement names them, and that order isn't alphabetical, so the test pins the list for one pair. A BatchExecuteStatement SELECT on a composite table that gives the partition key but not the sort key is refused like any other member without the full primary key. All four gave the same answers on three runs each in eu-west-2 and us-east-1 on 2026-11-14.

Renaming or removing a released test, or changing a region's recorded answer, no longer fails the checks on its own pull request. The committed results are now checked against the suite and registry as they stood at the release they were measured at, as the rest of the published board already was, rather than against main. The change reaches the board at the next release, when every target is re-run. A board is now refused if real DynamoDB's own run, in its own region, fails a test or passes one on a split row with an answer recorded for a different region.

A project's own row on the board now names its configuration beside the project, as the README table already did, so ExtendDB's row reads "ExtendDB · PostgreSQL" before its other builds are opened. The ways to run a target gain one more, OS package, for an operating system package: a .deb or .rpm, or an apt or dnf repository.

AWS Emulator joins the board, suggested by @exoego in #304. It is AWS's own multi-service emulator, written in Rust, with DynamoDB and DynamoDB Streams among the services it serves. It installs from a Linux package, or on other systems runs in Docker from an image built with the Dockerfile in its user guide. It serves HTTPS and checks SigV4 signatures by default, with a certificate and key it generates on each start, and it is measured that way.

Alternator joins the board. It is ScyllaDB's DynamoDB-compatible API, built into the database node itself rather than run as a separate emulator, with global secondary indexes on materialised views and Streams on change data capture. It runs from the official ScyllaDB container image, and its version column shows the ScyllaDB release the node reports.

ExtendDB's MongoDB backend joins the run as a third build of the same release, beside PostgreSQL and SQLite. It runs against a single-node MongoDB 7.0 replica set and is held to the same TLS, SigV4 and IAM posture as the other two, so the storage engine is again the only thing that differs between them. ExtendDB's PostgreSQL row now lists its official Docker image beside the source.

A target whose run is not scored now publishes as one everywhere. Its badge reads not scored in grey rather than going missing, and its row in the results table reads not scored where the letter would be. Neither the table nor the board gives it a region count, because a cohort is only ever read off a scored headline, and its page says no region has a figure rather than naming a headline region. It still sits below every lettered row. The rule itself doesn't change: a run that gets no answer to any one test is not scored.

Phoenix-Adapters joins the board. It is an Apache project serving the DynamoDB API as a REST layer over Apache Phoenix on HBase, so the row measures an adapter over an external store rather than a self-contained emulator. There is no release yet, so it is built from main with the project's own Docker setup and the row records the commit it ran.

npm run suite:manifest no longer writes into results/. It lists the suite by running it against an endpoint nothing answers, and that run wrote its own "provisioning never completed" file beside the results of whichever target the shell named. With CONFORMANCE_TARGET exported, that target then showed as not scored until the file was deleted, and with nothing set it replaced the one a real local run had left. The listing run now keeps everything in a temporary directory and ignores the caller's target, results directory, endpoint and AWS settings (#342).

Five index tests now have a timeout longer than the waits inside them, which corrects an earlier note in this section: in these five an expired wait could still end as a failure. Two vector index tests could wait up to 20 seconds longer than their timeouts allowed, and three GSI validation tests waited up to 2 minutes for a new table inside the 30-second default. The test runner ended them first, so a slow target got a failure where it should have got no answer. No published result came near the old limits, so no verdict changes.

Floci's row no longer lists Scoop. Its link pointed at a repository that doesn't exist, and Floci's own install instructions don't mention Scoop.

Every target now names its licence. Each target's page shows it in How to run it, next to what the target needs, and each project's entry in the emulator directory shows it under What you need. In both places it is the licence's name, linked to its text or to the vendor's terms. Where a licence has an SPDX identifier, that identifier is the name shown. Builds of one project show the project's licence. Where the thing the suite runs is licensed differently from its source repository, the licence shown is the one for what is run. Each target in /data/latest.json carries the same fact as licence, with name, url and, where one exists, spdx. The one licence remark that sat in a target's run note has moved into the field, so no target carries a line about its licence that the others do not.

LocalStack's name in the results table, and the project links on its pages, now point at localstack.cloud rather than its GitHub repository, which is archived.

A test expecting an error now says so plainly when the request was accepted: expected ValidationException, but the request was accepted, where it used to read expected AssertionError: expected "should have thrown" ... to be an instance of DynamoDBServiceException. The verdict is the same, a failure. What does change is a request that got no answer while a test was waiting for an error. A throttle that outlasted the SDK's retries, a transport fault or a 5xx other than 501 (not implemented, which stays a real failure) used to be judged as the wrong error and recorded as a failure. It is now recorded as no answer, the same as anywhere else in the suite, so a run that meets one is not scored rather than carrying a failure for it. A test that expects one of those errors on purpose still passes when it gets it. This covers tests that use expectDynamoError. Tests that catch the error by hand are unchanged for now.

The sweep's confirmation re-runs now run the test they are meant to repeat (#332). On the 2026-10-31, 2026-11-07 and 2026-11-14 sweeps every confirmation re-run selected no test, so all 16 split candidates were discarded as not reproduced. A candidate that cannot be re-run is now reported on a confirmation-error issue rather than discarded.

The six TransactWriteItems and TransactGetItems tests on malformed numbers and duplicate set members now pin eu-west-2's answer, from the current validation layer, where they accepted either layer's. us-east-1, eu-west-1 and us-west-2, which gave the older layer's answer in October, have moved. On 2026-11-13 every region that answered gave the current layer's answer to all of them except ap-south-1 and me-central-1, and a run of the six tests on 2026-11-14 found ap-south-1 on the current layer as well. Six new rows in registry/splits.json record me-central-1 on the older layer, which reads 1e2147483647 as an underflow and prints set members as sent. An engine that answers these six in the older layer now fails them, and is credited only against me-central-1. me-central-1 has missed the sweeps since 2026-10-17 and is not among the regions the board scores against, so for now such an engine fails them everywhere the board shows. The answers are in captures/2026-11-14-transaction-value-layers.json.

A not-scored row now says why it is not scored, where it used to print its sentences with a dash in place of each figure. Its row on the board and its directory entry say how many of its tests got no answer, or that the whole run did. Its page and the text corpus say the same, and add the reason the suite recorded for each kind (a transport failure or 5xx, a table that never became active, and so on) and what the answered tests did. A row that implements none of the suite says that instead. The page lists the tests that got no answer by operation, each with its reason, and no longer lists them among the failures as divergences they never were. The counts above the lists, and the row's counts in the data endpoints, are read from the same results as the lists, so the failed count is the number of failures listed. The methodology gains a section stating the rule.

The rest of the row reads the same way. A run that got no answer at all lists every operation and feature as not scored, with no pass or fail counts beneath them and no findings, where it used to show figures tallied from tests the run never answered. A feature holding some tests that got no answer reads as not scored too, as an operation holding one already did, rather than wearing a support state read from the rest. The data endpoints add indeterminate to each row's counts, tiers, operation areas and features, so the counts add up to the total on a row that is not scored as on any other; give an area or feature where nothing was observed the state unanswered rather than unsupported; and withhold correctness, and each region's pass rate, wherever the other two figures are withheld. Movement says when a target loses its score or gets one, as not scored and scored, instead of reading unchanged on both runs.

Grade not scored - first run