fix(dynamodb): order Query by full composite sort key

[ngencic]

Summary

Query ordered results using only the first RANGE attribute returned by
getSortKeyName(). For an index with a composite sort key (more than one RANGE
attribute, e.g. state RANGE, createdAt RANGE), the remaining components were
ignored: when the first component tied across rows, the stable sort left items
in base-table storage order and ScanIndexForward=false merely reversed that
order, so the secondary component (e.g. createdAt) never drove ordering.

Sort by the full sort key instead — comparing each RANGE attribute in
key-schema order, short-circuiting on the first non-equal component, then
reversing for ScanIndexForward=false. Single-sort-key indexes are unaffected
(a one-element list preserves previous behavior).

Adds getSortKeyNames() to GlobalSecondaryIndex, LocalSecondaryIndex and
TableDefinition.

Closes #1675

Type of change

• Bug fix (fix:)
• New feature (feat:)
• Breaking change (feat!: or fix!:)
• Docs / chore

AWS Compatibility

Incorrect behavior: a Query against an index with a multi-attribute composite
sort key returned items that were not ordered by the full key. Ties on the first
sort-key attribute fell back to storage order, and ScanIndexForward=false only
reversed that — so results diverged from DynamoDB, which orders by the entire
composite sort key. DynamoDB natively supports composite sort keys on secondary
indexes, so emulating full-key ordering is required for parity.

Verified with a wire-protocol (DynamoDB_20120810.Query) integration test: a GSI
keyed [memberName HASH, state RANGE, createdAt RANGE], items whose storage
order deliberately disagrees with createdAt, asserting ascending order and the
exact reverse for ScanIndexForward=false.

Checklist

• ./mvnw test passes locally
• New or updated integration test added
• Commit messages follow Conventional Commits

[greptile-apps]

Greptile Summary

The PR fixes DynamoDB Query ordering and pagination for secondary indexes with composite sort keys.

• Collects every RANGE attribute in key-schema order.
• Sorts query results lexicographically across the complete composite sort key.
• Includes all composite index components and base-table identity in pagination cursors.
• Adds unit and wire-protocol integration coverage for ascending, descending, and paginated queries.

Confidence Score: 5/5

The PR appears safe to merge.

The previously reported pagination identity issue is fixed by carrying every composite index component plus the base-table keys in LastEvaluatedKey and matching resumed index queries by the unique base-table key; no blocking failure remains.

Important Files Changed

Filename	Overview
src/main/java/io/github/hectorvent/floci/services/dynamodb/DynamoDbService.java	Query ordering now compares every composite sort-key component, while pagination emits and consumes a uniquely identifying cursor.
src/main/java/io/github/hectorvent/floci/services/dynamodb/model/GlobalSecondaryIndex.java	Adds ordered retrieval of all RANGE attribute names for GSI query ordering.
src/main/java/io/github/hectorvent/floci/services/dynamodb/model/LocalSecondaryIndex.java	Adds ordered retrieval of all RANGE attribute names for LSI query ordering.
src/main/java/io/github/hectorvent/floci/services/dynamodb/model/TableDefinition.java	Exposes all table RANGE attribute names while retaining the existing first-sort-key accessor.
src/test/java/io/github/hectorvent/floci/services/dynamodb/DynamoDbCompositeSortKeyQueryIntegrationTest.java	Adds wire-protocol coverage for full composite ordering, reverse ordering, cursor shape, and complete page traversal.
src/test/java/io/github/hectorvent/floci/services/dynamodb/DynamoDbServiceTest.java	Adds service-level regression coverage for ascending and descending composite GSI ordering.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    Q[Query request] --> K[Resolve table or index key schema]
    K --> F[Filter matching and non-expired items]
    F --> S[Compare all RANGE attributes in schema order]
    S --> D{ScanIndexForward false?}
    D -->|Yes| R[Reverse ordered results]
    D -->|No| P[Keep ascending order]
    R --> C[Apply ExclusiveStartKey]
    P --> C
    C --> L[Apply Limit or response-size cutoff]
    L --> E[Emit cursor with index components and base-table keys]

Loading

_{Reviews (3): Last reviewed commit: "fix(dynamodb): paginate composite sort-k..." | Re-trigger Greptile}

[hectorvent]

Thank you for this, and for fixing the cursor path along with the visible ordering symptom, the pagination collapse for rows sharing the first range value was the subtler half of the bug.

One context note rather than a change request: a multi range key schema is a Floci extension, real DynamoDB caps KeySchema at one partition plus one sort key, so this improves behavior on a surface AWS itself would reject at CreateTable. Since the single sort key path is preserved by construction and the extension already exists, that is fine here, it is just worth both of us knowing where the deviation line sits.

(blocking) Commit cf8bfbc carries an AI co-author trailer; this repo keeps commit attribution with human contributors (see AGENTS.md). Would you amend that commit and force push so the attribution is yours alone?

That attribution fix is the only blocker, the code itself is ready.