You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Semyon Danilov (Jira)" <ji...@apache.org> on 2023/06/16 12:02:00 UTC

[jira] [Commented] (IGNITE-19732) Cache IDs of configured tables

    [ https://issues.apache.org/jira/browse/IGNITE-19732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733477#comment-17733477 ] 

Semyon Danilov commented on IGNITE-19732:
-----------------------------------------

Thank you for the contribution. The patch looks good to me, merged to the main branch

> Cache IDs of configured tables
> ------------------------------
>
>                 Key: IGNITE-19732
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19732
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> IGNITE-19665 demonstrates that checks for 'whether a table with the given ID exists' take too much time as each of them parses whole tables configuration.
> We should cache the configured table IDs in a consistent way: that is, if this set has changed in the configuration, the cache should be invalidated (and refilled with fresh data).



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