You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2023/09/21 15:14:00 UTC
[jira] [Comment Edited] (IGNITE-20019) Introduce SystemViewManager
[ https://issues.apache.org/jira/browse/IGNITE-20019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767604#comment-17767604 ]
Pavel Pereslegin edited comment on IGNITE-20019 at 9/21/23 3:14 PM:
--------------------------------------------------------------------
[~korlov], [~mzhuravkov],
do a review of the proposed changes, please.
was (Author: xtern):
[~korlov], [~mzhuravkov], do a review of the proposed changes, please.
> Introduce SystemViewManager
> ---------------------------
>
> Key: IGNITE-20019
> URL: https://issues.apache.org/jira/browse/IGNITE-20019
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SystemViewManager is a component responsible for managing the system views':
> * during start, any component may register view definition to the view manager. View manager must ensure that there is no clashes in the views' names.
> * before node is going to be validated, view manager must enhance node attributes (LogicalNode class) with list of clusterViews registered so far. Later, sql engine will be using this information to map queries over cluster views properly
> * after node has passed validation and ready to join logical topology, view manager must register all views to the catalog.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)