[
https://issues.apache.org/jira/browse/IGNITE-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov resolved IGNITE-12441.
--------------------------------------
Resolution: Fixed
Merged to master.
[~alex_pl] Thanks, for the contribution.
> Refactor SystemViewRowAttributeWalker registration for system views
> -------------------------------------------------------------------
>
> Key: IGNITE-12441
> URL: https://issues.apache.org/jira/browse/IGNITE-12441
> Project: Ignite
> Issue Type: Task
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: IEP-35
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, to register system view we need at least to actions:
> # Register walker for a system view class
> # Register system view itself for a given class
> There is a map maintained to bind the attribute walker and system view class.
> Sometimes walker registration code and system view registration code are
> located in different parts of Ignite.
> But in most cases, there is 1:1 relation between attribute walkers and system
> views. We don't need to maintain additional structures and do additional
> actions to find a walker by system view class, we can bind walker to system
> view itself and can do it atomically.
> Moreover, in the current implementation, there is impossible to use different
> walkers for one system view class (for example when we want to create two
> views with the same system view class, but with different columns set)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
