You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/01/26 13:16:00 UTC
[jira] [Updated] (JCRVLT-496) Clarify usage of oak:index in
application packages
[ https://issues.apache.org/jira/browse/JCRVLT-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated JCRVLT-496:
-----------------------------------
Description:
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.
was:
Although according to JCRVLT-170 application packages must not contain oak index definitions, this is necessary 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.
> 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
> 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)