Skip to content

Conversation

@florianl
Copy link
Contributor

@florianl florianl commented Nov 19, 2025

Description

pcommon.Timestamp better represents a point in time rather than a duration. So keeping the proto field type for DurationNano is a better fit.

Corresponding Collector-contrib change: open-telemetry/opentelemetry-collector-contrib#44397

ping @open-telemetry/profiling-approvers

Link to tracking issue

Fixes #

Testing

Documentation

pcommon.Timestamp better represents a point in time rather than a duration. So
keeping the proto field type for DurationNano is a better fit.

Signed-off-by: Florian Lehner <[email protected]>
@dmathieu
Copy link
Member

Could you also open the -contrib PR that fixes the tests there?

@florianl
Copy link
Contributor Author

Could you also open the -contrib PR that fixes the tests there?

open-telemetry/opentelemetry-collector-contrib#44397

# Use this changelog template to create an entry for release notes.

# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
change_type: breaking
Copy link
Member

Choose a reason for hiding this comment

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

This is not a breaking change anymore. There should be 2 changelog entries.
An enhancement for the new method, and a deprecation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants