[BEAM-6118] Maven dependency conflicts between google-cloud-pubsub and Apache Beam packages

• Type: Bug
• Status: Open
• Priority: P3
• Resolution: Unresolved
• Affects Version/s: 2.5.0
• Component/s: io-java-gcp
• Labels: maven
• Assignee: Unassigned
• Reporter: Chris
• Created: 23/Nov/18 05:28
• Updated: 03/Jun/22 22:47

Description

(I'm using BDD terminology to phrase the issue)

 

AS A DEVELOPER I want to be able to use the following Maven dependencies (or newer versions) in the same Java project inside Eclipse SO THAT I can subscribe to a Google pub/sub independently from the mechanism supplied by Apache Beam, and efficiently update a dataset linked to my Apache Beam dataflow.

I want to update my linked dataset by accepting push data that reflects changes to its data, instead of having to poll for new data each time I process an item from an Apache Beam pipeline that subscribes to a different Google pub/sub dataset.

 

<dependency>
    <groupId>com.google.cloud.dataflow</groupId>
    <artifactId>google-cloud-dataflow-java-sdk-all</artifactId>  <version>2.5.0</version>
</dependency>

<dependency>
  <groupId>com.google.cloud</groupId>
  <artifactId>google-cloud-pubsub</artifactId>
  <version>1.53.0</version>
</dependency>

 

ACCEPTANCE CRITERIA

No dependency conflict related to io.grpc:grpc-core:jar is caused when I run

mvn clean install

against the project.

Please see here (I documented itas a GitHub issue against the google-cloud-pubsub library, however it's primarily a Beam Maven dependency issue):

 

https://github.com/googleapis/google-cloud-java/issues/4095