You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Amelchev Nikita (Jira)" <ji...@apache.org> on 2021/05/11 14:22:00 UTC
[jira] [Updated] (IGNITE-14675) Refactor
IgniteAuthenticationProcessor callbacks
[ https://issues.apache.org/jira/browse/IGNITE-14675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amelchev Nikita updated IGNITE-14675:
-------------------------------------
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required)
> 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)