[
https://issues.apache.org/jira/browse/IGNITE-8600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8600:
-----------------------------------
Description:
Currently our index cursor materializes rows as soon as they are encountered in
an index page. This is necessary to protect ourselves from concurrent data
modification. However, materialized rows might be filtered out later due to
additional filters. In addition, there is a chance that only indexed fields is
needed by query.
We can do the following:
1) Introduce new mode that will return partially materialized rows, with only
inline index fields initialized. When some non-initialized attribute is
requested, we go to data page and materialize the whole row
2) Enable this mode for MVCC by default
3) Optionally enable this mode for non-MVCC read-only mode through additional
flag.
> SQL: lazy row materialization
> -----------------------------
>
> Key: IGNITE-8600
> URL: https://issues.apache.org/jira/browse/IGNITE-8600
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.5
> Reporter: Vladimir Ozerov
> Priority: Major
> Labels: performance
>
> Currently our index cursor materializes rows as soon as they are encountered
> in an index page. This is necessary to protect ourselves from concurrent data
> modification. However, materialized rows might be filtered out later due to
> additional filters. In addition, there is a chance that only indexed fields
> is needed by query.
> We can do the following:
> 1) Introduce new mode that will return partially materialized rows, with only
> inline index fields initialized. When some non-initialized attribute is
> requested, we go to data page and materialize the whole row
> 2) Enable this mode for MVCC by default
> 3) Optionally enable this mode for non-MVCC read-only mode through additional
> flag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
