ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (IGNITE-7026) Index-organized data storage format
Date Tue, 12 Feb 2019 09:47:00 GMT

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

Vladimir Ozerov closed IGNITE-7026.

> Index-organized data storage format
> -----------------------------------
>                 Key: IGNITE-7026
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7026
>             Project: Ignite
>          Issue Type: Task
>          Components: cache, sql
>            Reporter: Vladimir Ozerov
>            Priority: Major
> In SQL *index-organized* table is a type of table format where rows are stored as leafs
of a primary key index (sometimes called "clustered index"). In this format data within a
single page is sorted in accordance with PK index. All leaves are always sorted as well. 
> Another table format is *heap*. Data is put into arbitrary page with enough space. Free
space is tracked using either free-lists or allocation maps. Primary key index is organized
in the same way as secondary index - leaf pages contain a kind of row pointer. This is how
Ignite currently works. 
> This ticket is aimed to implement index-organized storage format, which will give us
the following advantages:
> 1) Fast scans over PK index due to decreased number of page reads and page locks, which
is especially important for JOINs and OLAP cases;
> 2) Faster inserts in OLTP workloads due to less number of page updates.

This message was sent by Atlassian JIRA

View raw message