[Data] Use metrics from OpRuntimeMetrics for Progress#60304
Merged
Conversation
Signed-off-by: Daniel Shin <kyuseung1016@gmail.com>
![gemini-code-assist[bot]](https://cdn.statically.io/img/avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request is a good refactoring that removes the redundant output_row_count field from OpState and uses the row_outputs_taken metric from OpRuntimeMetrics instead. This change simplifies state management and improves code clarity by eliminating a duplicate counter. The update is consistently applied across all progress bar implementations (logging, rich, and tqdm). The logic appears sound, and I approve of this change.
ray-gardener
Bot
added
data
bveeramani
approved these changes
Jan 20, 2026
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
2 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.
Description
We had a separate field in
OpStateto keep track of outputted rows.OpRuntimeMetricsexist perPhysicalOperator, and also has a field to keep track of outputted rows, so there is no need to keep track of a duplicate in OpState.Related issues
N/A
Additional information
N/A