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

Alexander Lapin updated IGNITE-18141:
-------------------------------------
    Description: 
h3. Motivation

In order to bind table to some non-default distribution zone following syntax 
is suggested
{code:java}
CREATE TABLE ... WITH PRIMARY_ZONE = primary_zone; {code}
h3. Definition of Done
 * It's possible to create table binded to any existing distribution zone using 
suql with syntax.
 * It's not possible to change distribution zone - corresponding exception 
should be thrown. 

h3. Implementation Notes

Seems that it'll be necessary to add zone link to table configuration, probably 
using zone id. Let's check how it works for index to table bindings. 

Within the scope of with syntax processing we may use with replicas as a 
reference implementation.

  was:
h3. Motivation

 


> Add ability to bind tables with distribution zones on table creation
> --------------------------------------------------------------------
>
>                 Key: IGNITE-18141
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18141
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexander Lapin
>            Priority: Major
>              Labels: ignite-3
>
> h3. Motivation
> In order to bind table to some non-default distribution zone following syntax 
> is suggested
> {code:java}
> CREATE TABLE ... WITH PRIMARY_ZONE = primary_zone; {code}
> h3. Definition of Done
>  * It's possible to create table binded to any existing distribution zone 
> using suql with syntax.
>  * It's not possible to change distribution zone - corresponding exception 
> should be thrown. 
> h3. Implementation Notes
> Seems that it'll be necessary to add zone link to table configuration, 
> probably using zone id. Let's check how it works for index to table bindings. 
> Within the scope of with syntax processing we may use with replicas as a 
> reference implementation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to