You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Tao Yang (Jira)" <ji...@apache.org> on 2020/02/18 01:08:00 UTC

[jira] [Commented] (CALCITE-1861) Spatial Indexes

    [ https://issues.apache.org/jira/browse/CALCITE-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038707#comment-17038707 ] 

Tao Yang commented on CALCITE-1861:
-----------------------------------

[~julianhyde] Hi Julian, I found that the Hilbert curve function and the function that transfers region to index on Hilbert curve index have been implemented by using 'com.google.uzaygezen.core.CompactHilbertCurve' and related packages.  

Spatial Rules that optimize the ST_Within is also implemented. 

But in LogicalProject, there is a HILBERT=[$4], meaning we need to select from a column that has the index on the curve. Is this HILBERT column maintained in the memory or in the database? How does Apache Calcite generate and maintain this column( might be a B+tree)? 

> 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)