[
https://issues.apache.org/jira/browse/FLINK-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606184#comment-15606184
]
ASF GitHub Bot commented on FLINK-4864:
---------------------------------------
Github user rmetzger commented on the issue:
https://github.com/apache/flink/pull/2673
Thank you for looking into the details of this. If the user who ran into
the issue is using Java, they can fix the issue themselves by relocating our or
their Calcite version locally.
If the user uses Scala, we could look into fixing the issue with a patch to
the shade plugin (maybe using a custom
[transformer](https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#transformers)?)
Since I ran into the issue before I suspect that we'll run into the issue
again.
> 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)
