[
https://issues.apache.org/jira/browse/IGNITE-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995592#comment-16995592
]
Ignite TC Bot commented on IGNITE-12441:
----------------------------------------
{panel:title=Branch: [pull/7136/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4835348&buildTypeId=IgniteTests24Java8_RunAll]
> 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: 10m
> 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)
