feat: Allow specifying the engine for validate and filter#364
Merged
Conversation
Oliver Borchert (borchero)
requested review from
Andreas Albert (AndreasAlbertQC) and
Daniel Elsner (delsner)
as code owners
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #364 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 56 56
Lines 3481 3481
=========================================
Hits 3481 3481 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Andreas Albert (AndreasAlbertQC)
approved these changes
Jul 7, 2026
Daniel Elsner (delsner)
approved these changes
Jul 7, 2026
Co-authored-by: ElisabethBrockhausQC <125682683+ElisabethBrockhausQC@users.noreply.github.com>
Oliver Borchert (borchero)
changed the title
validate and filtervalidate and filter
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
4 participants
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.
Motivation
The streaming engine is sometimes faster; this speedup should accessible to the user.
In our benchmark, specifying
engine="streaming"results in slowdowns of ~30-40% because ofmaintain_order="left"in our joins (which is ~2.5x faster on the in-memory engine compared to the streaming engine).