[
https://issues.apache.org/jira/browse/CALCITE-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016774#comment-17016774
]
Julian Hyde commented on CALCITE-1861:
--------------------------------------
[~txy2539], I have now rebased my
[1861-spatial|https://github.com/julianhyde/calcite/commits/1861-spatial]
branch. There are a few test failures, but the build basically works. Review
the last 16 or so commits on that branch, and see which files I have been
changing. I apologize that the branch is a mixture of things - in addition to
spatial, I'm trying to make table-valued functions work more reliably, and a
few commits that fix up after rebasing.
In particular, look at changes I made to spatial.iq and RelOptRulesTest.xml.
These are both test files, and they give a clue as to what I was doing in the
rest of the code.
An easy way to start might be to implement one or two geospatial SQL functions.
Lots of them are listed in spatial.iq with '# Not implemented' comments. What
[~mmior] did in [17cd76af7|https://github.com/apache/calcite/commit/17cd76af7],
CALCITE-2031, is a good template to follow.
Much more advanced is to use algebraic transforms to implement particular
spatial queries efficiently. The testSpatialXxx methods in RelOptRulesTest are
examples.
> Spatial Indexes
> ---------------
>
> Key: CALCITE-1861
> URL: https://issues.apache.org/jira/browse/CALCITE-1861
> Project: Calcite
> Issue Type: Improvement
> Components: spatial
> Reporter: Atri Sharma
> Priority: Major
>
> 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)
