[jira] [Updated] (IGNITE-21803) Add integration tests making sure that public API methods inspecting schema use schema sync properly

["Roman Puchkovskiy (Jira)" <ji...@apache.org>]

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

Roman Puchkovskiy updated IGNITE-21803:
---------------------------------------
    Description: 
There are APIs for getting information from the schema (Table allows to get tables, JDBC provides access to the schema via Metadata, there are system views like the one that lists all indexes).

They should work consistently:
 # When preparing a result, the same catalog version is to be used
 # The catalog version must be active (no 'future' versions should be returned)
 # Schema synchronization must be done before getting the schema version (this guarantees that the APIs don't return stale data if the corresponding node lags with respect to the Metastorage)

  was:
There are APIs for getting information from the schema (Table allows to get tables, JDBC provides access to the schema via Metadata, there are system views like the one that lists all indexes).

They should work consistently:
 # When preparing a result, the same catalog version is to be used
 # The catalog version must be active
 # Schema synchronization must be done before getting the schema version (this guarantees that the APIs don't return stale data if the corresponding node lags with respect to the Metastorage)


> Add integration tests making sure that public API methods inspecting schema use schema sync properly
> ----------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-21803
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21803
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>
> There are APIs for getting information from the schema (Table allows to get tables, JDBC provides access to the schema via Metadata, there are system views like the one that lists all indexes).
> They should work consistently:
>  # When preparing a result, the same catalog version is to be used
>  # The catalog version must be active (no 'future' versions should be returned)
>  # Schema synchronization must be done before getting the schema version (this guarantees that the APIs don't return stale data if the corresponding node lags with respect to the Metastorage)



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