-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Latest Datastore + Pubsub clients libraries conflict #2503
Copy link
Copy link
Closed
Labels
api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.api: pubsubIssues related to the Pub/Sub API.Issues related to the Pub/Sub API.dependenciespriority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.triaged for GAtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Metadata
Metadata
Assignees
Labels
api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.api: pubsubIssues related to the Pub/Sub API.Issues related to the Pub/Sub API.dependenciespriority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.triaged for GAtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
I had a project with the latest datastore client (1.7.0) and added the pubsub client (0.25.0-beta).
When I tried to publish a message, it would not publish my message and hang forever with no error
after making some tests I found out those two clients had a conflict in their dependencies.
Datastore uses com.google.cloud.datastore:datastore-v1-protos:jar:1.3.0 that depends on com.google.protobuf:protobuf-java:jar:3.0.0 while PubSub uses com.google.cloud:google-cloud-core-grpc:jar:1.7.0 that depends on com.google.protobuf:protobuf-java:jar:3.3.1
I made it work excluding protobuf-java from the datastore dependency: