[
https://issues.apache.org/jira/browse/IGNITE-16342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-16342:
---------------------------------------
Summary: Support table rename (was: Handlin an table updates except a
schema)
> Support table rename
> --------------------
>
> Key: IGNITE-16342
> URL: https://issues.apache.org/jira/browse/IGNITE-16342
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> Table manager triggers a local event when a table is creating a new schema.
> But the scenario is not only for the table configuration: partitions,
> replicas and assignments also can be changed.
> Need to determine a process of handling the modification and which Table
> manager events are triggered for them.
> This issue concerns several configuration changes (name, assignment,
> partition, replicas) part of them is already handled, but TableMnager throws
> a local event for none of them.
> 1) Changing name is not handling and has no an event. I think the change have
> to be developed (handling change and creation of new event
> {{TableEvent#RENAME}}) as a part of the issue.
> 2) Changing assignment is already handling, but has no an event. Required to
> add the event {{TableEvent#REASSIGNMENT}}.
> 3) Changing partition did not ever design. Throw a critical error when
> configuration change happened is enough.
> 4) Changing replicas did not design, but probably may be implemented in
> another issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
