ibzib commented on pull request #14953: URL: https://github.com/apache/beam/pull/14953#issuecomment-887935720
> From the stack trace, > > ``` > at com.fasterxml.jackson.databind.ObjectMapper.findModules(ObjectMapper.java:1054) > > at org.apache.beam.sdk.options.PipelineOptionsFactory.<clinit>(PipelineOptionsFactory.java:471) > ``` > > it looks like Beam's `PipelineOptionsFactory` needs this dependency. > > https://github.com/apache/beam/blob/243128a8fc52798e1b58b0cf1a271d95ee7aa241/sdks/java/core/src/main/java/org/apache/beam/sdk/options/PipelineOptionsFactory.java#L25 It's not that simple unfortunately. While Beam depends on some Jackson artifacts, it does not and should not depend on the artifact `jackson-module-jaxb-annotations` (containing package `com.fasterxml.jackson.module.jaxb`). The problem is that somehow `com.fasterxml.jackson.module.jaxb.JaxbAnnotationModule` is erroneously being registered as a [service provider](https://docs.oracle.com/javase/8/docs/api/java/util/ServiceLoader.html?is-external=true) for `com.fasterxml.jackson.databind.Module` (which is part of Jackson core, which is a real Beam dependency). So our best guess so far is that the JaxbAnnotationModule service is being registered by some dependency which is common to Dataproc and EMR. -- 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]
