-
Notifications
You must be signed in to change notification settings - Fork 231
How to use jaeger-thrift classifier thrift92 right? #228
Comments
Thanks for creating this issue, it seems that this functionality is broken.
A reasonable way of fixing this would be to move all the thrift related code ( @yurishkuro Any objections to moving this code? (It breaks backwards compatibility with people directly instantiating the Sender because they would have to update the import statement) |
what does the current (relevant) dependency tree look like in terms of classes? I agree that it should be jaeger-core -> jaeger-thrift, but perhaps at the class level we can fix it without breaking the API. |
in The simplest backwards compatible fix I see is to do this:
|
Yes, this is exactly what I'm suggesting, I'll have a PR up in a bit. |
any plan on this issue? |
Apologies, we had prioritized other things, I'll get back to this sometime this week. |
Hi there, I’m also having issues with thrift versions and unfortunately the fixes introduced with v0.27.0-RC1 were not enough :(
After running missing-link I found another related with ThriftSender:
Thank you so much for the effort! Really helpful! I'll try to find some time to reciprocate with a PR. ;) Cheers |
Re-opening to deal with additional dependencies on apache thrift. |
My project thrift version is 0.5.0,so it's conflict with jaeger-thrift,so I follow the docs to use classifier thrift92,but when i replace the pom ,I found it's not compatible with jaeger-core.
because the jaeger-core UdpSender is dependent on org.apache.thrift.protocol.TCompactProtocol,
org.apache.thrift.protocol.TProtocolFactory ,and in class com.uber.jaeger.agent.thrift.Agent.Client#Client(org.apache.thrift.protocol.TProtocol),it's constructor use original thrift,how can i use org.shadow.apache.thrift92 (classifier thrift92 supplied ),not org.apache.thrift to avoid conflict? rewrite the UdpSender and ThriftUdpTransport and any relation class that dependent on org.apache.thrift ?
The text was updated successfully, but these errors were encountered: