Repository navigation
Conversation
|
|
|
|
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.
Rationale for this change
Passing a negative value to
Dataset.head()can result in unexpected behavior, including returning a table with a negative number of rows.Since the
head()API expects a non-negative number of rows, negative values should be rejected explicitly with a clear error message.What changes are included in this PR?
AsyncScanner::Head()to reject negativenum_rowsvalues.Status::Invalid("num_rows must be non-negative")when a negative value is provided.Dataset.head()Scanner.head()Fragment.head()Are these changes tested?
Yes.
python/pyarrow/tests/test_dataset.pytest suite: 310 passed, 54 skipped.git diff --checkpassed.Are there any user-facing changes?
Yes. Calling
Dataset.head(),Scanner.head(), orFragment.head()with a negativenum_rowsnow raisespyarrow.ArrowInvalidwith a clear error message instead of producing unexpected behavior.Was AI used for this PR?
PR code and description written by:
Reviewed before submission by: