Skip to content

feat: expose dynamic filter completion state#8

Open
discord9 wants to merge 1 commit into
GreptimeTeam:greptimedb-53.1.0-function-signature-exec-errorfrom
discord9:fix/dynamic-filter-is-complete
Open

feat: expose dynamic filter completion state#8
discord9 wants to merge 1 commit into
GreptimeTeam:greptimedb-53.1.0-function-signature-exec-errorfrom
discord9:fix/dynamic-filter-is-complete

Conversation

@discord9

Copy link
Copy Markdown

What changed

Expose a non-blocking DynamicFilterPhysicalExpr::is_complete() getter and add tests for its completion-state semantics.

Why

GreptimeDB remote dynamic filter initial snapshots need to capture whether the producer-side dynamic filter is already complete without awaiting wait_complete(). DynamicFilterPhysicalExpr already tracks this state internally and wait_complete() reads it as a fast path, so this exposes that state as a documented snapshot-style API.

The getter is intentionally non-blocking and does not synchronize with concurrent updates. Callers that need to wait for completion should continue to use wait_complete().

Tests

  • cargo fmt --all -- --check
  • cargo test -p datafusion-physical-expr dynamic_filter --lib

Signed-off-by: discord9 <discord9@163.com>
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