Skip to content

Fix custom metric display#20643

Merged
gabotechs merged 1 commit intomainfrom
fix-custom-metric-display
Mar 3, 2026
Merged

Fix custom metric display#20643
gabotechs merged 1 commit intomainfrom
fix-custom-metric-display

Conversation

@gabotechs
Copy link
Copy Markdown
Contributor

@gabotechs gabotechs commented Mar 2, 2026

Which issue does this PR close?

Rationale for this change

The custom metrics display is unnecessarily prepending the name of the metric during the display:

network_latency_min_2=name:network_latency_min 274.88µs

When it should just be:

network_latency_min_2=274.88µs

What changes are included in this PR?

Fix to the display

Are these changes tested?

yes, by a new test

Are there any user-facing changes?

@github-actions github-actions Bot added the physical-expr Changes to the physical-expr crates label Mar 2, 2026
Copy link
Copy Markdown
Member

@xudong963 xudong963 left a comment

Choose a reason for hiding this comment

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

Thank you!

@gabotechs gabotechs added this pull request to the merge queue Mar 3, 2026
Merged via the queue into main with commit 657887d Mar 3, 2026
62 of 63 checks passed
@alamb alamb deleted the fix-custom-metric-display branch March 17, 2026 18:09
de-bgunter pushed a commit to de-bgunter/datafusion that referenced this pull request Mar 24, 2026
## Which issue does this PR close?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes apache#123` indicates that this PR will close issue apache#123.
-->

- Closes part of
datafusion-contrib/datafusion-distributed#361.

## Rationale for this change

<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->

The custom metrics display is unnecessarily prepending the name of the
metric during the display:

```
network_latency_min_2=name:network_latency_min 274.88µs
```

When it should just be:
```
network_latency_min_2=274.88µs
```

## What changes are included in this PR?

<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

Fix to the display

## Are these changes tested?

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

yes, by a new test

## Are there any user-facing changes?

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->

<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
gabotechs added a commit to DataDog/datafusion that referenced this pull request Apr 23, 2026
## Which issue does this PR close?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes apache#123` indicates that this PR will close issue apache#123.
-->

- Closes part of
datafusion-contrib/datafusion-distributed#361.

## Rationale for this change

<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->

The custom metrics display is unnecessarily prepending the name of the
metric during the display:

```
network_latency_min_2=name:network_latency_min 274.88µs
```

When it should just be:
```
network_latency_min_2=274.88µs
```

## What changes are included in this PR?

<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

Fix to the display

## Are these changes tested?

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

yes, by a new test

## Are there any user-facing changes?

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->

<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->

(cherry picked from commit 657887d)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

physical-expr Changes to the physical-expr crates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants