[
https://issues.apache.org/jira/browse/BEAM-8331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943340#comment-16943340
]
Kai Jiang commented on BEAM-8331:
---------------------------------
sure. I assigned to myself.
> Vendored calcite breaks if another calcite is on the class path
> ---------------------------------------------------------------
>
> Key: BEAM-8331
> URL: https://issues.apache.org/jira/browse/BEAM-8331
> Project: Beam
> Issue Type: Bug
> Components: dsl-sql
> Affects Versions: 2.15.0, 2.16.0
> Reporter: Andrew Pilloud
> Priority: Major
>
> If the beam vendored calcite and a non-vendored calcite are both on the
> classpath, neither version works. This is because the non-JDBC calcite path
> uses JDBC as a easy way to perform reflection. (This affects the non-JDBC
> version of calcite.) We need to rewrite the calcite JDBC urls as part of our
> vendoring (for example 'jdbc:calcite:' to 'jdbc:beam-vendor-calcite:').
> Example of where this happens:
> [https://github.com/apache/calcite/blob/0cce229903a845a7b8ed36cf86d6078fd82d73d3/core/src/main/java/org/apache/calcite/tools/Frameworks.java#L175]
>
> {code:java}
> java.lang.RuntimeException: java.lang.RuntimeException: Property
> 'org.apache.beam.sdk.extensions.sql.impl.planner.BeamRelDataTypeSystem' not
> valid for plugin type org.apache.calcite.rel.type.RelDataTypeSystem
> at
> org.apache.beam.vendor.calcite.v1_20_0.org.apache.calcite.tools.Frameworks.withPrepare(Frameworks.java:160)
> at
> org.apache.beam.vendor.calcite.v1_20_0.org.apache.calcite.tools.Frameworks.withPlanner(Frameworks.java:115)
> at
> org.apache.beam.sdk.extensions.sql.zetasql.ZetaSQLPlannerImpl.<init>(ZetaSQLPlannerImpl.java:86)
> at
> org.apache.beam.sdk.extensions.sql.zetasql.ZetaSQLQueryPlanner.<init>(ZetaSQLQueryPlanner.java:55){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
