[
https://issues.apache.org/jira/browse/IGNITE-17310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev reassigned IGNITE-17310:
--------------------------------------------
Assignee: Aleksandr Polovtcev
> Intergrate IndexStorage into a TableStorage API
> -----------------------------------------------
>
> Key: IGNITE-17310
> URL: https://issues.apache.org/jira/browse/IGNITE-17310
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Assignee: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
>
> As an endpoint, we need an interface that represents a single index storage
> for a single partition. But, creating/destroying these storages is not as
> obvious from API standpoint.
> When index is created, storages should be created for every existing
> partition. And when a partition is created, index storages should be created
> for it as well. This complicates things a little bit, but, generally
> speaking, something like this could be a solution:
> * CompletableFuture<?> createIndex(indexCinfgiguration);
> * CompletableFuture<?> dropIndex(indexId);
> * IndexMvStorage getIndexStorage(indexId, partitionId);
> Build / rebuild API will be figured out later in another issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
