[ 
https://issues.apache.org/jira/browse/FLINK-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932537#comment-15932537
 ] 

Su Ralph commented on FLINK-6126:
---------------------------------

This looks due to incorrect local build of flink.

Documentation at 
https://ci.apache.org/projects/flink/flink-docs-release-1.2/setup/building.html 
shows clearly that 

"""
NOTE: Maven 3.3.x can build Flink, but will not properly shade away certain 
dependencies. Maven 3.0.3 creates the libraries properly. To build unit tests 
with Java 8, use Java 8u51 or above to prevent failures in unit tests that use 
the PowerMock runner.

"""
My local flink jar was build by maven3.3.3, which the shade of guava is not 
well set. Cause the conflict of elastic search(guava 18) and the packaged 
ones(should be the ones from hadoop related).




> Yet another conflict : guava
> ----------------------------
>
>                 Key: FLINK-6126
>                 URL: https://issues.apache.org/jira/browse/FLINK-6126
>             Project: Flink
>          Issue Type: Bug
>          Components: Build System, Local Runtime
>    Affects Versions: 1.2.0
>         Environment: Latest SNAPSHOT
>            Reporter: Su Ralph
>
> When write a user function try to write to elastic search (depend on 
> elasticsearch 2.3.5)
> Stack like:
> java.lang.NoSuchMethodError: 
> com.google.common.util.concurrent.MoreExecutors.directExecutor()Ljava/util/concurrent/Executor;
>         at 
> org.elasticsearch.threadpool.ThreadPool.<clinit>(ThreadPool.java:190)
>         at 
> org.elasticsearch.client.transport.TransportClient$Builder.build(TransportClient.java:131)
>         at 
> io.sherlock.capabilities.es.AbstractEsSink.open(AbstractEsSink.java:98)
> When enable env.java.opts.taskmanager to -version:class, we can see the class 
> load log like:
> [Loaded com.google.common.util.concurrent.MoreExecutors from 
> file:/opt/flink/lib/flink-dist_2.11-1.2.0.jar]
> The user code is using guva of 18.0.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to