You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The Keys and AttributeDefinitions lists in the undefined-index-key sentence differ from the service #554
The Some index key attributes are not defined in AttributeDefinitions. Keys: [..], AttributeDefinitions: [..] sentence renders its two lists differently from the service, on both CreateTable and UpdateTable.
Measured 2026-10-25 (us-east-1), index with keys g HASH and r RANGE unless stated:
Invalid KeySchema: Some index key attribute have no definition
Keys: [g], AttributeDefinitions: [pk]
keys a HASH, b RANGE, definitions [pk, a]
Keys: [a, b], AttributeDefinitions: [a, pk]
Keys: [b], AttributeDefinitions: [pk, a]
definitions [zz, pk, aa], key b missing
Keys: [b], AttributeDefinitions: [zz, aa, pk]
Keys: [b], AttributeDefinitions: [zz, pk, aa]
Three differences: the service's Keys list carries every key of the index, not the missing ones; two or more missing keys with a non-empty member answer the Invalid KeySchema sentence (the one #548 encodes for the empty member); and the service renders both lists in an order that is neither the request's nor alphabetical ([zz, pk, aa] renders [zz, aa, pk], [pk, n, b] renders [n, b, pk]), consistent across repeats, so it is not reproducible from the request.
Fix shape
Render every index key in Keys; answer two or more missing keys with Invalid KeySchema: Some index key attribute have no definition; keep request order for the lists and record the order difference in the differences document. Both paths: crates/core/src/validation/mod.rs (CreateTable) and crates/engine/src/update_table.rs (UpdateTable). The wire rows in #548 use one-key shapes, where the lists have one element, and pass on the service.
Activity