[
https://issues.apache.org/jira/browse/OAK-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483762#comment-16483762
]
Thomas Mueller commented on OAK-7501:
-------------------------------------
The component oak-query-spi is currently (mainly) used as a link between the
query engine (in oak core) and the index implementations (in oak-lucene for
example). That was the intention of oak-query-spi (spi for service provider
interface, where an index implementation is a service).
Your change adds things to oak-query-spi that are not really needed by an index
implementation, but are needed by oak code that creates indexes. This is
slightly different usage.
What about adding this to oak-api instead of oak-query-spi?
> 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)
