[
https://issues.apache.org/jira/browse/JCRVLT-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289956#comment-17289956
]
Dominik Süß commented on JCRVLT-496:
------------------------------------
Ah right - the trouble here is that the index definitions live outside of the
application scope (libs&apps) but are required while deploying. The problem
being that mutable content is not being installed at the time the image with
the immutable paths are installed - a solution for customers would be to create
this definition with sling-repoinit.
So yes I think it is a fair call to make index definitions an exception to the
rule and also considered as application content.
> 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)
