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 (JIRA)" <ji...@apache.org> on 2018/05/17 16:35:00 UTC
[jira] [Commented] (OAK-7501) Dependencies on IndexUtils
[ https://issues.apache.org/jira/browse/OAK-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479330#comment-16479330 ]
angela commented on OAK-7501:
-----------------------------
[~stillalex], , [~rombert], another patch to drop usage of implementation details (this time index utilities) within the oak security code base that will ultimately allow us to drop dependencies to _oak-core_ and potentially even refactor security code out of _oak-core_. I split the patch in 2 parts:
- proposed enhancements to indexing ([~tmueller], [~chetanm], i would also appreciate your feedback on this part)
- adjustment of the security code base to use the new interface instead of using {{IndexUtils}} and rely on implementation details on how the index definitions are store.
> Dependencies on IndexUtils
> --------------------------
>
> Key: OAK-7501
> URL: https://issues.apache.org/jira/browse/OAK-7501
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core, indexing, security
> Reporter: angela
> Priority: Major
> Attachments: OAK-7501-adjust_security.patch, OAK-7501-indexing.patch
>
>
> There are several places across the oak security code base where {{IndexUtils}} is used to create index definitions. In addition these usages hardcode implementation details on how the index definitions are stored.
> The goal is to make the security code independant of the very details of the index machinery and ultimately allow the indexing team to change/replace the way indices are store and how requirements like e.g. uniqueness are met.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)