[
https://issues.apache.org/jira/browse/IGNITE-15718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15718:
---------------------------------
Description:
The method (TableManager#table(String)), where we are waiting for a table
creation by name, is not correct, because we can see an 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 the table, but the name unique
only in one time). Need to wait for 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, has been fixed, it is time to
fix method _TableManager#isTableConfigured(String)_.
UPD:
Direct value for _TableManager#isTableConfigured(String)_ has been done in
IGNITE-15881
was:
The method (TableManager#table(String)), where we are waiting for a table
creation by name, is not correct, because we can see an 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 the table, but the name unique
only in one time). Need to wait for 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, has been fixed, it is time to
fix method _TableManager#isTableConfigured(String)_.
> 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
> Assignee: Mirza Aliev
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The method (TableManager#table(String)), where we are waiting for a table
> creation by name, is not correct, because we can see an 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 the table, but the name
> unique only in one time). Need to wait for 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, has been fixed, it is time
> to fix method _TableManager#isTableConfigured(String)_.
> UPD:
> Direct value for _TableManager#isTableConfigured(String)_ has been done in
> IGNITE-15881
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
