[
https://issues.apache.org/jira/browse/CALCITE-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181364#comment-17181364
]
Julian Hyde commented on CALCITE-1861:
--------------------------------------
[~dsmiley], Your point is well-taken. We use the ESRI stuff for the bulk of the
ST_ functions, and it's working for now, so there's no forcing function for us
to change it. Our query rewrites are in terms of the standard functions (E.g.
{{ST_DWithin}}) so if we were to switch, the query rewrites would be unaffected.
The ESRI stuff does not support space-filling curves, so for this change I
copy-pasted (and translated from Scala to Java) a couple of classes from a
different LocationTech project,
[SFCurve|https://github.com/locationtech/sfcurve].
> Spatial index, based on Hilbert space-filling curve
> ---------------------------------------------------
>
> Key: CALCITE-1861
> URL: https://issues.apache.org/jira/browse/CALCITE-1861
> Project: Calcite
> Issue Type: Improvement
> Components: spatial
> Reporter: Atri Sharma
> Assignee: Julian Hyde
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.26.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Many Calcite users, like Phoenix and Flink can benefit from support of
> Spatial indexes.
> See:
> http://revenant.ca/www/postgis/workshop/indexing.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
