[
https://issues.apache.org/jira/browse/CALCITE-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180003#comment-17180003
]
Michael Mior commented on CALCITE-1861:
---------------------------------------
[~julianhyde]: What [~txy2539] ended up doing is creating a Postgres UDF based
on the same Hilbert code to define a computed column in Postgres with an index
so that it could be used for query rewriting. This works pretty well end-to-end
although there are a lot of practical concerns to solve with this setup. The
UDF was installed manually and the column with the Hilbert value was hardcoded
when ideally this would be read from the Postgres catalog.
> 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: 10m
> 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)
