[
https://issues.apache.org/jira/browse/CALCITE-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612155#comment-17612155
]
Julian Hyde commented on CALCITE-4294:
--------------------------------------
{quote}
other projects may include different versions [of JTS and Proj4j] in their
classpath
{quote}
If those projects follow semantic versioning, we should be OK. We, and the
other projects, can easily upgrade to the latest version, which will have all
the features needed by us and the other projects.
Shading is often suggested as a solution to this problem, but causes other
problems (e.g. unaddressed security issues).
Calcite's policy with Guava has been to support - and test against - a wide
range of versions.
> Use JTS rather than ESRI as the underlying library for geospatial (ST_)
> functions
> ---------------------------------------------------------------------------------
>
> Key: CALCITE-4294
> URL: https://issues.apache.org/jira/browse/CALCITE-4294
> Project: Calcite
> Issue Type: Bug
> Components: spatial
> Reporter: Julian Hyde
> Assignee: Bertil Chapuis
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.32.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The geospatial functions are currently implemented using the ESRI library. We
> should consider using JTS instead. AT the time we started work on geospatial
> the JTS did not have a suitable license, but this is no longer the case. I
> gather that JTS is a superior library.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
