[
https://issues.apache.org/jira/browse/CALCITE-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039408#comment-17039408
]
Michael Mior edited comment on CALCITE-1861 at 2/18/20 7:58 PM:
----------------------------------------------------------------
[~txy2539] Right now, this is a predicate that is explicitly mentioned in the
query. That is, the rule matches a condition on the query that looks like
{{hilbertColumn = hilbert(latitude, longitude)}}. For testing, you can start
with just creating a table populated with the appropriate values. That is, you
would have the columns {{latitude}}, {{longitude}}, and {{hilbertColumn}} where
the last column contains the pre-computed position on the Hilbert curve. This
could probably be replaced later with a view which defines {{hilbertColumn}} or
as a stored column computed via UDF in the underlying database.
was (Author: michaelmior):
[~txy2539] Right now, this is a predicate that is explicitly mentioned in the
query. That is, the rule matches a condition on the query that looks like
{{hilbertColumn = hilbert(latitude, longitude)}}. For testing, you can start
with just creating a table populated with the appropriate values. That is, you
would have the columns {{latitude}}, {{longitude}}, and {{hilbertColumn}} where
the last column contains the pre-computed position on the Hilbert curve. This
could probably be replaced later with a view which defines {{hilbertColumn}}.
> 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)
