test: compare native arrow reader with pyarrow scans#6
Draft
abnobdoss wants to merge 1 commit into
Draft
Conversation
00b1cc9 to
4ae56ff
Compare
3163619 to
a4ccc0e
Compare
4ae56ff to
443819e
Compare
a4ccc0e to
67c4bf9
Compare
443819e to
abe8da0
Compare
67c4bf9 to
5b181ea
Compare
abe8da0 to
bb205f9
Compare
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.
Stack position: Python PR after #5 (ABA-167).
Adds integration-style comparisons between default PyArrow scans and opt-in native Arrow batch reader scans.
Validation reported by implementer:
Current status: draft, under Codex red-team review. Known red-team focus: env var semantics, whether
to_arrow()is actually native, fixture reliability, skip/import placement, and comparison robustness.