[
https://issues.apache.org/jira/browse/IGNITE-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730515#comment-17730515
]
Andrey Mashenkov commented on IGNITE-19687:
-------------------------------------------
{quote}* Add support ALTER ZONE <zone_name> SET DEFAULT to reassign default
zone.
* Allow renaming for all zones.{quote}
Most likely, this may be fixed as a separate task.
> Support default distribution zone reassignment.
> -----------------------------------------------
>
> Key: IGNITE-19687
> URL: https://issues.apache.org/jira/browse/IGNITE-19687
> Project: Ignite
> Issue Type: Improvement
> Reporter: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3
>
> *Motivation.*
> We have no reasonable arguments that we need a special distribution zone
> instance. All distribution zones are equals. Thus, conceptually, any zone can
> be used as default one and can be renamed.
> For better UX, we still can require at least one distribution zone, which is
> currently assigned as default zone, must always exists.
> Let's
> * Avoid using any hardcoded zone id or zone name for getting or detecting the
> default distribution zone.
> * Distributed zone manager shouldn't care which zone is default. Catalog will
> be responsible for resolving default zone if it is not specified when table
> is creating.
> * Add a property in Configuration that will to default zone by zone id.
> * A distribution zone with name "Default"(?) and some default parameters must
> be created on cluster initialization phase and an id, which was assigned to
> such zone, must be stored to Configuration.
> * Forbid dropping of distribution zone, which is currently marked as default.
> * Add support {{ALTER ZONE <zone_name> SET DEFAULT}} to reassign default zone.
> * Allow renaming for all zones.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
