[
https://issues.apache.org/jira/browse/IGNITE-27478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-27478:
-------------------------------------
Description:
Since we actually treat default zones as a sort of "hello world" aspect and
thus do not expect for them to be used in production, following items should be
implemented:
* Add an ability for the user to nullify the default zone. We should properly
handle that, since at the moment of nullification of the default zone, it may
not yet exist due to the lazy nature of creating one when creating a table.
* If the default zone was nullified and the user tries to create a table
without a link to a zone - an exception should be thrown.
* In the default zone wasn't nullified, and the user creates a table without a
link to a zone - table should be created (already implemented) along with
printing a warning to a log regarding default zone usage.
* Documentation should be updated not only with the aforementioned aspects but
also with a general notification that a default zone in production is a bad
practice.
> Rework default zone initiation logic
> ------------------------------------
>
> Key: IGNITE-27478
> URL: https://issues.apache.org/jira/browse/IGNITE-27478
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Priority: Major
> Labels: ignite-3
>
> Since we actually treat default zones as a sort of "hello world" aspect and
> thus do not expect for them to be used in production, following items should
> be implemented:
> * Add an ability for the user to nullify the default zone. We should
> properly handle that, since at the moment of nullification of the default
> zone, it may not yet exist due to the lazy nature of creating one when
> creating a table.
> * If the default zone was nullified and the user tries to create a table
> without a link to a zone - an exception should be thrown.
> * In the default zone wasn't nullified, and the user creates a table without
> a link to a zone - table should be created (already implemented) along with
> printing a warning to a log regarding default zone usage.
> * Documentation should be updated not only with the aforementioned aspects
> but also with a general notification that a default zone in production is a
> bad practice.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
