[
https://issues.apache.org/jira/browse/IGNITE-21235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-21235:
-----------------------------------------
Description: IGNITE-21215 introduces an API for changing a table's name.
Unfortunately table names are cached on the server side inside
`TableManager#tablesByIdVv`. I currently use a hack to simply change the name
inside the cached object, but this is conceptually incorrect, because this
breaks the history of table updates. Probably this should be replaced either by
some immutable history or by removing the cached name from the object.
> Revisit the approach of changing the name of the table in TableImpl
> -------------------------------------------------------------------
>
> Key: IGNITE-21235
> URL: https://issues.apache.org/jira/browse/IGNITE-21235
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
>
> IGNITE-21215 introduces an API for changing a table's name. Unfortunately
> table names are cached on the server side inside `TableManager#tablesByIdVv`.
> I currently use a hack to simply change the name inside the cached object,
> but this is conceptually incorrect, because this breaks the history of table
> updates. Probably this should be replaced either by some immutable history or
> by removing the cached name from the object.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
