[
https://issues.apache.org/jira/browse/OAK-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487319#comment-16487319
]
Robert Munteanu commented on OAK-7501:
--------------------------------------
[~anchela] - my suggestion was rather to only pass it once to the repository
initializer, and then store it an intermediate object. Or to just create a
method that does all the steps
- create oak:index
- check if index exists
- create index if it does not exist
Of course, I might've missed something as I did not actually try that
refactoring.
> 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)
