You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Angela Schreiber (Jira)" <ji...@apache.org> on 2020/10/01 14:17:00 UTC

[jira] [Resolved] (OAK-5118) SynchronizationMBean: Deprecate syncAllUsers and syncAllExternalUsers

     [ https://issues.apache.org/jira/browse/OAK-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Angela Schreiber resolved OAK-5118.
-----------------------------------
    Resolution: Won't Fix

> SynchronizationMBean: Deprecate syncAllUsers and syncAllExternalUsers
> ---------------------------------------------------------------------
>
>                 Key: OAK-5118
>                 URL: https://issues.apache.org/jira/browse/OAK-5118
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: auth-external
>            Reporter: Angela Schreiber
>            Priority: Major
>
> The following 2 methods defined by {{SyncronizationMBean}} have been introduced with a warning about being potentially expensive [0]:
> - {{syncAllUsers}}
> - {{syncAllExternalUsers}}
> To me defining API that is designed with scalability issues in mind, looks like a troublesome pattern. As far as I understood from the history associated with this, I assume that it was introduced to allow for upfront sync to workaround other issues faced by sync-upon-login.
> With the latest improvements and features introduced wrt to the user-sync, I think we should move forward deprecating the troublesome methods for the upcoming 1.6 release.
> [0] Quote from Javadoc: "Note that this can be an expensive operation since all potential users need to be examined."



--
This message was sent by Atlassian Jira
(v8.3.4#803005)