Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use internal Marshaler in testing exporters instead of gRPC. #5332

Merged
merged 1 commit into from
Feb 10, 2022

Conversation

anuraaga
Copy link
Contributor

While working on #5314, I realized that as we are already overriding the exporters from what our normal javaagent (and smoke tests) use, there actually isn't a reason to care that much about whether gRPC or okhttp transport is used. And thinking more, then I realized that given our versions are always aligned, using some simple SDK internal APIs from our testing artifact seems like a reasonable, if slightly questionable, approach to avoid it all completely. I approve :) /cc @jkwatson @jack-berg in case you don't

@trask
Copy link
Member

trask commented Feb 10, 2022

we got 👍 from @jack-berg, so merging 😄

@trask trask merged commit 85f9f01 into open-telemetry:main Feb 10, 2022
RashmiRam pushed a commit to RashmiRam/opentelemetry-auto-instr-java that referenced this pull request May 23, 2022
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.

3 participants