[
https://issues.apache.org/jira/browse/IGNITE-21831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-21831:
-----------------------------------------
Description:
When implementing indexes restoration in IGNITE-21680 I messed up and didn't
notice, that all indexes are stored in the RocksDB instance without any
connection to their table IDs. Therefore, every table, started in the same data
region, got the same (full) set of indexes recovered.
Another problem is that right now it is impossible to drop a table only using
its ID, needed for IGNITE-21760, because we need to know, which indexes it has.
> RocksDb indexes are not table aware
> -----------------------------------
>
> Key: IGNITE-21831
> URL: https://issues.apache.org/jira/browse/IGNITE-21831
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksandr Polovtcev
> Assignee: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When implementing indexes restoration in IGNITE-21680 I messed up and didn't
> notice, that all indexes are stored in the RocksDB instance without any
> connection to their table IDs. Therefore, every table, started in the same
> data region, got the same (full) set of indexes recovered.
> Another problem is that right now it is impossible to drop a table only using
> its ID, needed for IGNITE-21760, because we need to know, which indexes it
> has.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
