[
https://issues.apache.org/jira/browse/IGNITE-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-7495:
------------------------------------
Description:
Recently we introduced a set of commands to control WAL state of particular
caches. I.e. using SQL API user could do the following to disable WAL in order
to speedup data load:
{code}
ALTER TABLE my_table NOLOGGING
{code}
Now consider that user has a lot of tables and would like to disable WAL for
the whole data region at once (e.g. to load data for the whole schema).
Currently to achieve this he would have to issue a number of commands for each
and every table.
Instead, we should provide tiered approach, when user could disable WAL for
both cache and data region. Proposed commands:
{code}
ALTER DATA REGION my_region NOLOGGING; // Disable for region
ALTER TABLE my_table NOLOGGING; // Disable for table
{code}
*NOTE*
Semantics of tiered behaviour should be designed carefully. E.g. it should be
possible to have a data region with disabled WAL, while still being able to
have a cache in it with enabled WAL. Please refer to Oracle's {{NOLOGGING}}
handling.
was:
Recently we introduced a set of commands to control WAL state of particular
caches. I.e. using SQL API user could do the following to disable WAL in order
to speedup data load:
{code}
ALTER TABLE my_table NOLOGGING
{code}
Now consider that user has a lot of tables and would like to disable WAL for
the whole data region at once (e.g. to load data for the whole schema).
Currently to achieve this he would have to issue a number of commands for each
and every table.
Instead, we should provide tiered approach, when user could disable WAL for
both cache and data region. Proposed commands:
{code}
ALTER DATA REGION my_region NOLOGGING; // Disable for region
ALTER TABLE my_table NOLOGGING; // Disable for table
{code}
*NOTE*
Semantics of tiered behaviour should be designed carefully. E.g. it should be
possible to have a data region with disabled WAL, while still being able to
have a cache in it with enabled WAL. Please refer to Oracle's {{NOLOGGING}}
handling.
> Ability to disable WAL globally for data region
> -----------------------------------------------
>
> Key: IGNITE-7495
> URL: https://issues.apache.org/jira/browse/IGNITE-7495
> Project: Ignite
> Issue Type: New Feature
> Components: cache
> Reporter: Vladimir Ozerov
> Priority: Major
> Fix For: 2.5
>
>
> Recently we introduced a set of commands to control WAL state of particular
> caches. I.e. using SQL API user could do the following to disable WAL in
> order to speedup data load:
> {code}
> ALTER TABLE my_table NOLOGGING
> {code}
> Now consider that user has a lot of tables and would like to disable WAL for
> the whole data region at once (e.g. to load data for the whole schema).
> Currently to achieve this he would have to issue a number of commands for
> each and every table.
> Instead, we should provide tiered approach, when user could disable WAL for
> both cache and data region. Proposed commands:
> {code}
> ALTER DATA REGION my_region NOLOGGING; // Disable for region
> ALTER TABLE my_table NOLOGGING; // Disable for table
> {code}
> *NOTE*
> Semantics of tiered behaviour should be designed carefully. E.g. it should be
> possible to have a data region with disabled WAL, while still being able to
> have a cache in it with enabled WAL. Please refer to Oracle's {{NOLOGGING}}
> handling.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
