[
https://issues.apache.org/jira/browse/IGNITE-17626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17626:
-------------------------------------
Description:
We need to figure out how dropping sorted and hash indexes for all storages
should work.
At the moment we have 2 api synchronous and asynchronous, also for some reason
there is only a drop in the index hash but not for sorted.
was:
Both sync and async versions of the operation should be implemented. Schema may
not be known at the moment of destruction.
Integrate it into tests.
Maybe implement destruction on start for indexes that had not finished their
completion before the restart.
> Fix drop sorted and hash indices for all storages
> -------------------------------------------------
>
> Key: IGNITE-17626
> URL: https://issues.apache.org/jira/browse/IGNITE-17626
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
>
> We need to figure out how dropping sorted and hash indexes for all storages
> should work.
> At the moment we have 2 api synchronous and asynchronous, also for some
> reason there is only a drop in the index hash but not for sorted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
