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

Roman Puchkovskiy updated IGNITE-22367:
---------------------------------------
    Description: 
Currently, all index metadata is stored in the Catalog. This is problematic, 
because
 # Some fields (like txWaitCatalogVersion) or states (like STOPPING) do not 
belong to the Catalog
 # The Catalog may be compacted making it impossible to get metadata from it

We need to create a storage (based on Vault) to store metadata for each index. 
An index entry can include (the list is rough):
 # Index ID
 # Name? (not sure if we need it; maybe for building messages for humans)
 # txWaitCatalogVersion
 # History of how the index changed its state (with activation timestamp of 
each transition)
 # Current state

The states set is broader than the set stored in the Catalog:
 * REGISTERED
 * BUILDING
 * AVAILABLE
 * STOPPED
 * READ_ONLY (this means that the index was dropped (maybe together with its 
table), it cannot be written to, it can not be used by any RW transactions, but 
can be read by RO transactions with correct readTimestamp)

The storage should 

> Create index metadata storage
> -----------------------------
>
>                 Key: IGNITE-22367
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22367
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> Currently, all index metadata is stored in the Catalog. This is problematic, 
> because
>  # Some fields (like txWaitCatalogVersion) or states (like STOPPING) do not 
> belong to the Catalog
>  # The Catalog may be compacted making it impossible to get metadata from it
> We need to create a storage (based on Vault) to store metadata for each 
> index. An index entry can include (the list is rough):
>  # Index ID
>  # Name? (not sure if we need it; maybe for building messages for humans)
>  # txWaitCatalogVersion
>  # History of how the index changed its state (with activation timestamp of 
> each transition)
>  # Current state
> The states set is broader than the set stored in the Catalog:
>  * REGISTERED
>  * BUILDING
>  * AVAILABLE
>  * STOPPED
>  * READ_ONLY (this means that the index was dropped (maybe together with its 
> table), it cannot be written to, it can not be used by any RW transactions, 
> but can be read by RO transactions with correct readTimestamp)
> The storage should 



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

Reply via email to