[python][ray] Fix update_by_row_id failure on empty datasets - #9217
Open
XiaoHongbo-Hope wants to merge 4 commits into
Open
[python][ray] Fix update_by_row_id failure on empty datasets#9217XiaoHongbo-Hope wants to merge 4 commits into
XiaoHongbo-Hope wants to merge 4 commits into
Conversation
XiaoHongbo-Hope
marked this pull request as ready for review
August 14, 2026 08:53
XiaoHongbo-Hope
changed the title
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
1 participant
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.
Purpose
Return a no-op result when a transformed Ray Dataset contains no rows.
Ray drops the schema of an empty shuffle input, so grouping an empty update by
_FIRST_ROW_IDcurrently fails withArrowInvalid: Invalid sort key column.This change adds an internal sentinel to preserve the shuffle schema and removes
it before writing. It does not pre-count or materialize the Dataset, so the
upstream computation is not executed twice.
Tests
{"num_updated": 0}and leaves the table unchanged.