You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/09/16 08:04:00 UTC

[jira] [Updated] (IGNITE-6407) SQL: CREATE INDEX command should build index bottom-up

     [ https://issues.apache.org/jira/browse/IGNITE-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ozerov updated IGNITE-6407:
------------------------------------
    Summary: SQL: CREATE INDEX command should build index bottom-up  (was: SQL: {{CREATE INDEX}} command should build index bottom-up)

> SQL: CREATE INDEX command should build index bottom-up
> ------------------------------------------------------
>
>                 Key: IGNITE-6407
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6407
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>    Affects Versions: 2.1
>            Reporter: Vladimir Ozerov
>              Labels: iep-1, performance
>
> Currently when {{CREATE INDEX}} command is executed, entires are added to index one-by-one. This leads to high index build times. 
> Instead, we can build index as follows:
> 1) Iterate over the whole data set and sort it according to index rules
> 2) Build leaf pages 
> 3) Build middle pages
> 4) Build root page
> This approach is used by many vendors. The main difficulty is that the whole data set may not fit to memory. For this reason we will need to implement a kind of disk spilling. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)