[
https://issues.apache.org/jira/browse/IGNITE-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-16765:
--------------------------------------
Description:
To make the work with scripts more convenient, we need to support an ability to
change default storage engine for an entire script.
>From user's point of view it should look like this:
{code:sql}
SET default_engine = <storage_engine_name>;
CREATE TABLE <table_name> (
<table_schema>
);
{code}
The scope of the SET expression is limited by DDL script execution context.
So, within this ticket we should introduce a support for SET command as well as
execution context that is bound to a script lifecycle.
was:
There must be an ability to define a storage engine for every table using the
following DDL syntax:
{code:sql}
CREATE TABLE <table_name> (
<table_schema>
)
ENGINE <storage_engine_name>;
{code}
It is possible to define a default storage engine in the following manner:
{code:sql}
SET default_engine = <storage_engine_name>;
CREATE TABLE <table_name> (
<table_schema>
);
{code}
Default storage engine parameter is not a durable property of a cluster. The
scope of the SET expression is limited by DDL script execution context.
It is impossible to change the storage engine for the table after creation
because it will lead to moving a big amount of data between different storages.
But a user could copy a table to another table which was created on a different
storage engine. Maybe such kind of action will be automated later.
> Support creation of table for specific storage engine
> -----------------------------------------------------
>
> Key: IGNITE-16765
> URL: https://issues.apache.org/jira/browse/IGNITE-16765
> Project: Ignite
> Issue Type: Task
> Reporter: Andrey N. Gura
> Priority: Major
> Labels: ignite-3
>
> To make the work with scripts more convenient, we need to support an ability
> to change default storage engine for an entire script.
> From user's point of view it should look like this:
> {code:sql}
> SET default_engine = <storage_engine_name>;
> CREATE TABLE <table_name> (
> <table_schema>
> );
> {code}
> The scope of the SET expression is limited by DDL script execution context.
> So, within this ticket we should introduce a support for SET command as well
> as execution context that is bound to a script lifecycle.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
