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

Uses shaded netty in server jar to avoid downstream conflicts. #1788

Merged
merged 1 commit into from
Nov 12, 2017

Conversation

codefromthecrypt
Copy link
Member

gRPC uses Netty 4.1 and netty-tcnative-boringssl-static, which is
sensitive to Netty versions. DataStax Cassandra driver 4.0 uses Netty
4.1, but the driver isn't out, yet. By using the published shaded jar,
we can dodge the conflict for now.

I've verified that we can connect to google cloud services after this
change. I've also verified that there's no significant jar size change.

See https://github.com/grpc/grpc-java/blob/master/SECURITY.md#netty
See openzipkin/zipkin-gcp#45

gRPC uses Netty 4.1 and `netty-tcnative-boringssl-static`, which is
sensitive to Netty versions. DataStax Cassandra driver 4.0 uses Netty
4.1, but the driver isn't out, yet. By using the published shaded jar,
we can dodge the conflict for now.

I've verified that we can connect to google cloud services after this
change. I've also verified that there's no significant jar size change.

See https://github.com/grpc/grpc-java/blob/master/SECURITY.md#netty
See openzipkin/zipkin-gcp#45
@codefromthecrypt
Copy link
Member Author

fyi @michaelsembwever @llinder

@codefromthecrypt
Copy link
Member Author

pps of course I also verified cassandra still works by manually starting a zipkin server with storage type set to both versions

@codefromthecrypt codefromthecrypt merged commit f934861 into master Nov 12, 2017
@codefromthecrypt codefromthecrypt deleted the no-more-netty branch November 12, 2017 00:43
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.

1 participant