OTel-Arrow exporter timeout propagation #34733
Conversation
github-actions
bot
added
cmd/otelcontribcol
mwear
added
the
ready to merge
…tor-contrib into jmacd/arrow_exporter_timeout
|
This has been approved for 2 weeks. Can it merge? |
Can I ask you to fix up the merge conflicts please? |
Of course! I fix the conflicts after every release, but this has been sitting for two release cycles and now I'll have to fix them twice. |
…tor-contrib into jmacd/arrow_exporter_timeout
songy23
removed
the
ready to merge
There was a problem hiding this comment.
Replace statements are out of date, please run "make crosslink" and commit the changes in this PR.
Please fix linter as well https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/10704184781/job/29676638560?pr=34733
…tor-contrib into jmacd/arrow_exporter_timeout
|
@songy23 Thank you. I appreciate your help. The linter changed while this PR was open,. I want to point out that this PR was approved and green following commit f735180 and again following commit 9e4d8e3. It takes a relatively large amount of work to keep these PRs green, and this is the third time. Please merge! |
songy23
added
the
ready to merge
**Description:** Exporter side of open-telemetry/otel-arrow#227. The receiver side is open-telemetry#34742. **Link to tracking Issue:** open-telemetry/otel-arrow#227 **Testing:** Adds a test for the expected metadata propagation. **Documentation:** Since this is expected of gRPC receivers, no docs are changed.
Description: Exporter side of open-telemetry/otel-arrow#227. The receiver side is #34742.
Link to tracking Issue: open-telemetry/otel-arrow#227
Testing: Adds a test for the expected metadata propagation.
Documentation: Since this is expected of gRPC receivers, no docs are changed.