Skip to content

[pkg/translator/zipkin] Unexport ToTranslator#43852

Merged
codeboten merged 1 commit into
open-telemetry:mainfrom
atoulme:zipkin_pkg_api
Oct 29, 2025
Merged

[pkg/translator/zipkin] Unexport ToTranslator#43852
codeboten merged 1 commit into
open-telemetry:mainfrom
atoulme:zipkin_pkg_api

Conversation

@atoulme

@atoulme atoulme commented Oct 28, 2025

Copy link
Copy Markdown
Contributor

This is a breaking change of this package: this struct is not used directly anywhere in contrib, and therefore it would make sense to no longer expose it. I would like to hear back if anyone is using this directly as API.

@codeboten codeboten merged commit 8342f30 into open-telemetry:main Oct 29, 2025
189 checks passed
@github-actions github-actions Bot added this to the next release milestone Oct 29, 2025
@atoulme atoulme deleted the zipkin_pkg_api branch October 29, 2025 18:36
dmitryax added a commit that referenced this pull request Nov 4, 2025
Reverts
#43852

Given that we provide pdata->zipkin API, we should keep providing the
curated API for Zipkin->pdata translation as long as we offer zipkin
receiver. It's being used in the Splunk distro where we don't want
diverge from the OTel specification.
jelly-afk pushed a commit to jelly-afk/opentelemetry-collector-contrib that referenced this pull request Nov 6, 2025
Reverts
open-telemetry#43852

Given that we provide pdata->zipkin API, we should keep providing the
curated API for Zipkin->pdata translation as long as we offer zipkin
receiver. It's being used in the Splunk distro where we don't want
diverge from the OTel specification.
dyl10s pushed a commit to dyl10s/opentelemetry-collector-contrib that referenced this pull request Nov 21, 2025
This is a breaking change of this package: this struct is not used
directly anywhere in contrib, and therefore it would make sense to no
longer expose it. I would like to hear back if anyone is using this
directly as API.
dyl10s pushed a commit to dyl10s/opentelemetry-collector-contrib that referenced this pull request Nov 21, 2025
Reverts
open-telemetry#43852

Given that we provide pdata->zipkin API, we should keep providing the
curated API for Zipkin->pdata translation as long as we offer zipkin
receiver. It's being used in the Splunk distro where we don't want
diverge from the OTel specification.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants