Stop development of exporter and receiver components in this repository #225
Comments
|
PR has been merged! 🎉 |
|
This is in progress. We will not develop new PRs in this repo, and the components will be deleted (which requires some effort). See also open-telemetry/opentelemetry-collector-contrib#33567. |
|
We will have to hold off on actually deleting the components here until the components are actually usable in a collector-contrib release. However, development has moved, see: [otelarrowreceiver] Ensure consume operations are not canceled at stream EOF |
Merged
jmacd
added a commit
that referenced
this issue
Jun 21, 2024
Same as open-telemetry/opentelemetry-collector-contrib#33688 but merging this code here will let me create and test a PR in that repository, whereas it will be messy to build off this work in the same repository. I expect this package to be deleted after open-telemetry/opentelemetry-collector-contrib#33688 and open-telemetry/opentelemetry-collector-contrib#33579 merged, as discussed in #225. Part of #227.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now the OTel-Arrow exporter and receiver components have been copied into https://github.com/open-telemetry/opentelemetry-collector-contrib, it has been difficult to develop in this repository. We were forced to continue development here because the components were unstable (especially so in the v0.22.0 release).
When open-telemetry/opentelemetry-collector-contrib#33518 merges, it will be an ideal time to remove the components from this repository. We will release v0.25.0 without those components and continue development in https://github.com/open-telemetry/opentelemetry-collector-contrib.
The text was updated successfully, but these errors were encountered: