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

Aleksandr Polovtcev updated IGNITE-21433:
-----------------------------------------
    Description: 
# Create an index, wait for it to be completely built (i.e. enter the AVAILABLE 
state)
 # Drop the index (it will move to the STOPPING state)
 # Try to create another index with the same name as the first index had

Currently, validation will fail and the index at step 3 will not be created.

This is because we validate that there is no index/table/schema with the same 
name in the Catalog.

The validation should be relaxed to ignore the 'already dropped' indices 
(namely, those that are in the STOPPING state).

  was:
# Create an index, wait for it to be completely built (i.e. enter the AVAILABLE 
state)
 # Drop the index (it will move to the STOPPING state)
 # Try to create another index with the same name as the first index had

Currently, validation will fail and the index at step 3 will not be created.

This is because we validate that there is no index/table/schema with the same 
name in the Catalog.

The validation should be laxed to ignore the 'already dropped' indices (namely, 
those that are in the STOPPING state).


> It is not possible to create an index with same name as a just dropped index 
> had
> --------------------------------------------------------------------------------
>
>                 Key: IGNITE-21433
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21433
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> # Create an index, wait for it to be completely built (i.e. enter the 
> AVAILABLE state)
>  # Drop the index (it will move to the STOPPING state)
>  # Try to create another index with the same name as the first index had
> Currently, validation will fail and the index at step 3 will not be created.
> This is because we validate that there is no index/table/schema with the same 
> name in the Catalog.
> The validation should be relaxed to ignore the 'already dropped' indices 
> (namely, those that are in the STOPPING state).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to