Skip to content

[VQueues] Optimize sys_vqueue_meta point lookups#5048

Draft
AhmedSoliman wants to merge 4 commits into
mainfrom
pr5048
Draft

[VQueues] Optimize sys_vqueue_meta point lookups#5048
AhmedSoliman wants to merge 4 commits into
mainfrom
pr5048

Conversation

@AhmedSoliman

@AhmedSoliman AhmedSoliman commented Jul 15, 2026

Copy link
Copy Markdown
Member

Use the generic exact ID selection machinery for sys_vqueue_meta so id equality and IN predicates route directly to the owning Restate partitions.

Add a targeted vqueue-meta read path backed by bounded RocksDB multi-get batches, while keeping range scans for scope and non-point predicates. Vqueue-meta ID range scans now use total-order iteration when the bounds span multiple partition keys.

Add DataFusion coverage for vqueue-meta point queries and NOT IN handling so negated lists remain normal filters instead of lookup inputs.


Stack created with Sapling. Best reviewed with ReviewStack.

@github-actions

github-actions Bot commented Jul 15, 2026

Copy link
Copy Markdown

Test Results

  8 files  ± 0    8 suites  ±0   2m 49s ⏱️ - 2m 13s
 43 tests  - 18   43 ✅  - 18  0 💤 ±0  0 ❌ ±0 
186 runs   - 82  186 ✅  - 82  0 💤 ±0  0 ❌ ±0 

Results for commit 9f81529. ± Comparison against base commit 47c66b3.

This pull request removes 18 tests.
dev.restate.sdktesting.tests.Combinators ‑ awakeableOrTimeoutUsingAwaitAny(Client)
dev.restate.sdktesting.tests.Combinators ‑ firstSuccessfulCompletedAwakeable(Client)
dev.restate.sdktesting.tests.Combinators ‑ mixedAllCompletedRunSignalAndFailedRun(Client)
dev.restate.sdktesting.tests.Combinators ‑ mixedAllSucceededRunAndSignal(Client)
dev.restate.sdktesting.tests.Combinators ‑ mixedRunWinsRaceAgainstSignal(Client)
dev.restate.sdktesting.tests.Combinators ‑ mixedSignalWinsAfterRunFails(Client)
dev.restate.sdktesting.tests.Combinators ‑ signalAllCompleted(Client)
dev.restate.sdktesting.tests.Combinators ‑ signalAllSuccessfulOrFirstFailed(Client)
dev.restate.sdktesting.tests.Combinators ‑ signalFirstCompleted(Client)
dev.restate.sdktesting.tests.Combinators ‑ signalFirstSuccessfulOrAllFailed(Client)
…

♻️ This comment has been updated with latest results.

NOT IN (...) and != predicates enumerate excluded values, but the partition-key extractor and the entry-id/invocation-id filters ignored InList::negated and built lookup sets or ranges from those excluded IDs.

Reject negated IN lists in those extractors so DataFusion keeps them as normal filters instead of treating them as positive lookup inputs.

Cover the sys_invocation_status regression with excluded and retained invocation IDs on different partition keys, and keep sys_vqueue_entry_status coverage for the same NOT IN behavior.
… reads

Keep equality and IN predicates as exact ID selections in the DataFusion filter layer instead of collapsing large sets into scan ranges. This lets point-lookup tables preserve the user's requested IDs while range-scan tables can still convert the same selection back to bounds.

Teach the partitioned table provider to group exact point reads by Restate partition when the scanner can re-fetch the exact IDs itself. Use that for sys_invocation_status by adding an InvocationIdSet scan path backed by bounded RocksDB multi-get batches.

Split partition-store inclusive key-range scans into single-prefix and total-order variants, and use total-order scans when invocation-status, journal, or journal-events ID bounds span multiple partition keys. This preserves correctness for range-scan consumers of exact ID selections.

Adapt the worker cleaner to the fallible stream shape used by the new invocation-status scan path, and add scan-mode coverage for the new total-order range variant.
Make sys_vqueue_entry_status understand exact entry_id predicates so equality and IN filters can be planned as targeted reads rather than broad partition scans. Entry IDs are parsed back to their partition keys for routing and displayed consistently from the stored EntryId representation.

Add the partition-store support needed to read selected entry-status records through bounded batched multi-get calls while preserving range scans for non-point predicates. Entry-id range scans now use total-order iteration when the bounds span multiple partition keys.

Only advertise partition_key ordering for sys_vqueue_entry_status, because the exposed entry_id string ordering does not match the raw on-disk entry-id ordering.

Cover both the DataFusion point-query path and multi-get batching behavior, including a NOT IN regression so excluded IDs are not treated as an exact lookup set.
Use the generic exact ID selection machinery for sys_vqueue_meta so id equality and IN predicates route directly to the owning Restate partitions.

Add a targeted vqueue-meta read path backed by bounded RocksDB multi-get batches, while keeping range scans for scope and non-point predicates. Vqueue-meta ID range scans now use total-order iteration when the bounds span multiple partition keys.

Add DataFusion coverage for vqueue-meta point queries and NOT IN handling so negated lists remain normal filters instead of lookup inputs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant