Skip to content

[Data] Use metrics from OpRuntimeMetrics for Progress#60304

Merged
bveeramani merged 1 commit intoray-project:masterfrom
kyuds:progress-opmetrics
Jan 20, 2026
Merged

[Data] Use metrics from OpRuntimeMetrics for Progress#60304
bveeramani merged 1 commit intoray-project:masterfrom
kyuds:progress-opmetrics

Conversation

@kyuds
Copy link
Copy Markdown
Member

@kyuds kyuds commented Jan 19, 2026

Description

We had a separate field in OpState to keep track of outputted rows. OpRuntimeMetrics exist per PhysicalOperator, 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

Signed-off-by: Daniel Shin <kyuseung1016@gmail.com>
@kyuds kyuds added the go add ONLY when ready to merge, run all tests label Jan 19, 2026
@kyuds kyuds requested a review from a team as a code owner January 19, 2026 21:18
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ray-gardener bot added data Ray Data-related issues observability Issues related to the Ray Dashboard, Logging, Metrics, Tracing, and/or Profiling community-contribution Contributed by the community labels Jan 20, 2026
@bveeramani bveeramani merged commit e5c3885 into ray-project:master Jan 20, 2026
5 checks passed
@kyuds kyuds deleted the progress-opmetrics branch January 20, 2026 05:40
jinbum-kim pushed a commit to jinbum-kim/ray that referenced this pull request Jan 29, 2026
…60304)

## Description
We had a separate field in `OpState` to keep track of outputted rows.
`OpRuntimeMetrics` exist per `PhysicalOperator`, 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

Signed-off-by: Daniel Shin <kyuseung1016@gmail.com>
Signed-off-by: jinbum-kim <jinbum9958@gmail.com>
400Ping pushed a commit to 400Ping/ray that referenced this pull request Feb 1, 2026
…60304)

## Description
We had a separate field in `OpState` to keep track of outputted rows.
`OpRuntimeMetrics` exist per `PhysicalOperator`, 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

Signed-off-by: Daniel Shin <kyuseung1016@gmail.com>
Signed-off-by: 400Ping <jiekaichang@apache.org>
ryanaoleary pushed a commit to ryanaoleary/ray that referenced this pull request Feb 3, 2026
…60304)

## Description
We had a separate field in `OpState` to keep track of outputted rows.
`OpRuntimeMetrics` exist per `PhysicalOperator`, 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

Signed-off-by: Daniel Shin <kyuseung1016@gmail.com>
peterxcli pushed a commit to peterxcli/ray that referenced this pull request Feb 25, 2026
…60304)

## Description
We had a separate field in `OpState` to keep track of outputted rows.
`OpRuntimeMetrics` exist per `PhysicalOperator`, 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

Signed-off-by: Daniel Shin <kyuseung1016@gmail.com>
Signed-off-by: peterxcli <peterxcli@gmail.com>
peterxcli pushed a commit to peterxcli/ray that referenced this pull request Feb 25, 2026
…60304)

## Description
We had a separate field in `OpState` to keep track of outputted rows.
`OpRuntimeMetrics` exist per `PhysicalOperator`, 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

Signed-off-by: Daniel Shin <kyuseung1016@gmail.com>
Signed-off-by: peterxcli <peterxcli@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-contribution Contributed by the community data Ray Data-related issues go add ONLY when ready to merge, run all tests observability Issues related to the Ray Dashboard, Logging, Metrics, Tracing, and/or Profiling

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants