VictorPlusC commented on pull request #14953: URL: https://github.com/apache/beam/pull/14953#issuecomment-1074152397
I believe so. Though for this, the versioning does not seem to have much of an effect here, I was able to successfully execute a job on Dataproc with both versions. As this dependency is necessary for me to fully enable an automatic process to send Flink pipelines to Dataproc, without needing users to locally build the shadowJar with it included, would it be possible to include only the `jackson-module-jaxb-annotations` dependency and have a Jira ticket with a to-do to remove it after it has been resolved on the Dataproc side? This way, we can guarantee that this dependency issue does not show up in a future version of Beam. Doing so will also make it possible for users to follow use-cases such as the content covered in the [Dataproc Flink component documentation](https://cloud.google.com/dataproc/docs/concepts/components/flink) using a version of Flink that has not been deprecated on the Beam side (the working example uses a Dataproc 1.5 image and Flink 1.9, but we no longer support that Flink version). Additionally, it does not appear that the `jackson-datatype-jsr310` dependency is needed for me to run Flink pipelines on Dataproc, so only adding the jaxb-annotations should suffice. +Dagang Wei (@functicons), who helped me investigate the dependencies on the Dataproc side. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
