[
https://issues.apache.org/jira/browse/OAK-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486804#comment-16486804
]
angela commented on OAK-7501:
-----------------------------
[~tmueller], i don't think that _oak-api_ is the right place. also, the way the
{{IndexUtils}} are designed today, prevents us from extracting an interface to
_oak-api_ due to the usage of {{NodeBuilder}}. For me _oak-query-spi_ felt
natural as there is also the {{QueryIndexProvider}}, which is used along side
with the {{IndexUtils}} in the security code base (namely in the
{{RepositoryInitializer}}, which again operates on {{NodeBuilders}}). But at
the end of the day I don't have a strong preference and would be equally fine
putting it in _oak-plugins_ (see OAK-7499).
> 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
> Labels: m12n
> 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)
