Repository navigation
test: cover remote dynamic filters with a work unit feed - #896
Open
raghavyadav01 wants to merge 1 commit into
Open
raghavyadav01 wants to merge 1 commit into
raghavyadav01 wants to merge 1 commit into
Conversation
A partitioned join with a work unit feed on the build side and a parquet scan on the probe side, in different stages. The join dynamic filter has to reach the scan through the coordinator while the feed streams its work units over the same channel. Signed-off-by: Raghav Yadav <raghavmnnit@gmail.com>
raghavyadav01
force-pushed
the
test/work-unit-feed-remote-dynamic-filters
branch
from
November 18, 2026 23:21
7fae510 to
cd5f547
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #770.
Adds
remote_dynamic_filters_with_feedtotests/work_unit_feed.rs. It runs a partitioned join with a work unit feed on the build side and the weather parquet scan on the probe side, so the join's dynamic filter has to go through the coordinator to reach the scan in another stage while the coordinator is also streaming the feed's work units.The test checks that:
Cloud9ambetween 0 and 1, matching the feed'spartitionvalues), viarewrite_distributed_plan_with_dynamic_filtersin the snapshot.The feed is on the build side because
RowGeneratorExecdoesn't accept pushed-down filters, so it can't be a filter consumer itself. Happy to extend it if you had a different case in mind.