Skip to content

docs: filter pushdown is connected, not future work - #9637

Open
jackylee-ch wants to merge 1 commit into
vortex-data:developfrom
jackylee-ch:spark-devguide-pushdown
Open

docs: filter pushdown is connected, not future work#9637
jackylee-ch wants to merge 1 commit into
vortex-data:developfrom
jackylee-ch:spark-devguide-pushdown

Conversation

@jackylee-ch

Copy link
Copy Markdown
Contributor

The guide called filter pushdown unconnected and "planned future work". It was connected in #7785:
VortexScanBuilder implements SupportsPushDownV2Filters and the converted expression reaches
native code as the ScanOptions filter, so a developer reading this plans around a limitation that
no longer exists.

The Future Work section keeps the Source trait migration, which is still outstanding.

Tests

make -C docs html succeeds under the repo's --fail-on-warning, same warning count as develop.

AI assistance

Written with agentic AI assistance; I traced the pushdown path end to end before editing.

VortexScanBuilder has implemented SupportsPushDownV2Filters since vortex-data#7785,
and the converted predicate reaches native code as the ScanOptions filter.
The guide still described it as infrastructure that exists but is not wired
up, so a developer reading it plans around a limitation that is gone.

The Future Work section keeps the Scan API Source trait migration, which is
still outstanding.

Signed-off-by: jackylee <qcsd2011@gmail.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