To enhance the performance of search queries, we created custom indexes. But while deploying this is causing Build Failures & Replication Queue is getting Blocked in Adobe AaCS.
Error trying to extract package at path /etc/packages/com.xxxxxgwi/aem-xxxxxgwi-project.ui.content-0.0.1-SNAPSHOT-cp2fm-converted.zip because of Failed to import /oak:index/xxxxxPageLucene-1 (javax.jcr.AccessDeniedException: Access denied.), the importer will retry later,
Stacktrace: org.apache.sling.distribution.common.DistributionException: Error trying to extract package at path /etc/packages/com.xxxxxgwi/aem-xxxxxgwi-project.ui.content-0.0.1-SNAPSHOT-cp2fm-converted.zip because of 'Failed to import /oak:index/xxxxxPageLucene-1 (javax.jcr.AccessDeniedException: Access denied.)'
at org.apache.sling.distribution.journal.bookkeeper.ContentPackageExtractor.handlePath(ContentPackageExtractor.java:87)...
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: org.apache.jackrabbit.vault.packaging.PackageException: Failed to import /oak:index/xxxxxPageLucene-1 (javax.jcr.AccessDeniedException: Access denied.)
at org.apache.sling.distribution.journal.bookkeeper.ContentPackageExtractor.failed(ContentPackageExtractor.java:126)
at org.apache.sling.distribution.journal.bookkeeper.ContentPackageExtractor.installPackage(ContentPackageExtractor.java:109)
at org.apache.sling.distribution.journal.bookkeeper.ContentPackageExtractor.handlePath(ContentPackageExtractor.java:81)
... 8 more
Caused by: org.apache.jackrabbit.vault.packaging.PackageException: javax.jcr.nodetype.ConstraintViolationException: OakConstraint0021: /oak:index/xxxxxAssetLucene-1[[oak:QueryIndexDefinition]]: Mandatory property type not found in a new node
at org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage.extract(ZipVaultPackage.java:237)
at org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.extract(JcrPackageImpl.java:401)
at org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.extract(JcrPackageImpl.java:360)
at org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.extract(JcrPackageImpl.java:346)
at org.apache.sling.distribution.journal.bookkeeper.ContentPackageExtractor.installPackage(ContentPackageExtractor.java:118)
at org.apache.sling.distribution.journal.bookkeeper.ContentPackageExtractor.installPackage(ContentPackageExtractor.java:106)
... 9 more
Caused by: javax.jcr.nodetype.ConstraintViolationException: OakConstraint0021: /oak:index/xxxxxAssetLucene-1[[oak:QueryIndexDefinition]]: Mandatory property type not found in a new node
at org.apache.jackrabbit.oak.api.CommitFailedException.asRepositoryException(CommitFailedException.java:226)...
Caused by: org.apache.jackrabbit.oak.api.CommitFailedException: OakConstraint0021: /oak:index/xxxxxAssetLucene-1[[oak:QueryIndexDefinition]]: Mandatory property type not found in a new node
at org.apache.jackrabbit.oak.plugins.nodetype.TypeEditor$1.onConstraintViolation(TypeEditor.java:109)
at org.apache.jackrabbit.oak.plugins.nodetype.TypeEditor.constraintViolation(TypeEditor.java:234)...
Please help me to understand what need to be changed to fix this issue.
Solved! Go to Solution.
Views
Replies
Total Likes
Oak indexes (/oak:index
) are specifically managed by the AEM as a Cloud Service deployment process. This is because the Cloud Manager must wait until any new index is deployed and fully re-indexed before switching over to the new code image.
For this reason, although Oak indexes are mutable at run time, they must be deployed as code so that they can be installed before any mutable packages are installed. Therefore /oak:index
configurations are part of the Code Package and not part of the Content Package as described below.
Oak indexes (/oak:index
) are specifically managed by the AEM as a Cloud Service deployment process. This is because the Cloud Manager must wait until any new index is deployed and fully re-indexed before switching over to the new code image.
For this reason, although Oak indexes are mutable at run time, they must be deployed as code so that they can be installed before any mutable packages are installed. Therefore /oak:index
configurations are part of the Code Package and not part of the Content Package as described below.