[
https://issues.apache.org/jira/browse/IGNITE-14675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339540#comment-17339540
]
Ignite TC Bot commented on IGNITE-14675:
----------------------------------------
{panel:title=Branch: [pull/9079/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9079/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5994513&buildTypeId=IgniteTests24Java8_RunAll]
> Refactor IgniteAuthenticationProcessor callbacks
> ------------------------------------------------
>
> Key: IGNITE-14675
> URL: https://issues.apache.org/jira/browse/IGNITE-14675
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Since IgniteAuthenticationProcessor is not treated as a separate processor,
> it is needed to refactor explicit IgniteAuthenticationProcessor callbacks
> from other processors. Many of them can be eliminated.
> For example onActivate method can be replaced with
> PartitionsExchangeAware#onDoneBeforeTopologyUnlock
> Explicit onLocalJoin method call can be replaced with
> discoMgr.localJoinFuture().listen(fut -> onLocalJoin());
> and so on.
> It is also possible that this will require changing the startup order of the
> IgniteAuthenticationProcessor.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
