[
https://issues.apache.org/jira/browse/FLINK-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604599#comment-15604599
]
ASF GitHub Bot commented on FLINK-4864:
---------------------------------------
Github user fhueske commented on the issue:
https://github.com/apache/flink/pull/2673
OK, I could reproduce the issue on my setup, but I have no idea why this
happens. I checked the jar file and the Calcite classes seem to be correctly
relocated (files are at correct location in jar file, import statements of
compiled classes are adapted) and also the Flink Table API classes are compiled
with adapted import statements. I created a new Flink project from the Scala
Quickstart and the compilation fails in IntelliJ and with Maven.
I guess we have to take a deeper look into this issue :-/
> Shade Calcite dependency in flink-table
> ---------------------------------------
>
> Key: FLINK-4864
> URL: https://issues.apache.org/jira/browse/FLINK-4864
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Affects Versions: 1.2.0
> Reporter: Fabian Hueske
> Assignee: Jark Wu
>
> The Table API has a dependency on Apache Calcite.
> A user reported to have version conflicts when having a own Calcite
> dependency in the classpath.
> The solution would be to shade away the Calcite dependency (Calcite's
> transitive dependencies are already shaded).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
