[jira] [Updated] (IGNITE-15718) Issues in implementation of the method TableManager#table(String)

["Vyacheslav Koptilin (Jira)" <ji...@apache.org>]

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

Vyacheslav Koptilin updated IGNITE-15718:
-----------------------------------------
    Fix Version/s: 3.0.0-alpha4

> Issues in implementation of the method TableManager#table(String)
> -----------------------------------------------------------------
>
>                 Key: IGNITE-15718
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15718
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha4
>
>
> In the method (TableManager#table(String)) where we are waiting for a table creation by name is not correct, because we can to see event about another table with the same name (it is possible when a node is lagging behind of other and is seeing outdated events about drop/create table, but the name unique only in one time). Need to make waiting of table creation by ID, because ID is unique for each table even on infinity time.
> Also, after the ticket (IGNITE-15412) where Configuration API was extended of possibility to read a Metasorage value directly, have been fixed, it is a time to fix method _TableManager#isTableConfigured(String)_.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)