[
https://issues.apache.org/jira/browse/JCRVLT-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290026#comment-17290026
]
Konrad Windszus commented on JCRVLT-496:
----------------------------------------
The patch introduces a flag: See
https://github.com/apache/jackrabbit-filevault/pull/124/files#diff-757a8aa9eac03a42c545be81f0a2efc430450bff88b94755259432f6faad74caR127
and
https://github.com/apache/jackrabbit-filevault/pull/124/files#diff-94ca8489565e8a80508dfb3a944f1c2afa1fb645fc58025085e5c5361a7dc7bbR57.
Now you can configure the immutable part.
> Clarify usage of oak:index in application packages
> --------------------------------------------------
>
> Key: JCRVLT-496
> URL: https://issues.apache.org/jira/browse/JCRVLT-496
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Affects Versions: 3.4.8
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 3.4.10
>
>
> Although according to JCRVLT-170 application packages must not contain oak
> index definitions, this is necessary though for AEM as a Cloud Service
> (https://experienceleague.adobe.com/docs/experience-manager-cloud-service/operations/indexing.html?lang=en#index-management-using-blue-green-deployments
> and
> https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem-project-content-package-structure.html?lang=en#mutable-vs-immutable).
> To allow validation of such application packages there should be a flag
> considered, which allows for oak index definitions inside application
> packages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
