Hello Team,
I checked out AEM Cloud Repo on my local and trying to deploy back to Cloud.
Update: I created a new pipeline for stage and prod deployment, they are also failing with the same error
16:45:33.345 [main] ERROR c.a.granite.indexing.tool.CompareCmd - Failed to compare indexes: Can not add a new customized index /oak:index/damAssetLucene-8-custom-1 because an index (possibly merged) named /oak:index/damAssetLucene-9 that has a higher major version already exists. As higher major versions take precedence, the new customized index will not be used. In order to resolve the problem, the new customized index needs to be merged with the latest index, and renamed, so that it has a higher version number than the latest index. Suggested name for new index: /oak:index/damAssetLucene-9-custom-1
com.adobe.granite.indexing.tool.IndexingException: Can not add a new customized index /oak:index/damAssetLucene-8-custom-1 because an index (possibly merged) named /oak:index/damAssetLucene-9 that has a higher major version already exists. As higher major versions take precedence, the new customized index will not be used. In order to resolve the problem, the new customized index needs to be merged with the latest index, and renamed, so that it has a higher version number than the latest index. Suggested name for new index: /oak:index/damAssetLucene-9-custom-1
at com.adobe.granite.indexing.tool.CompareCmd.compareIndexes(CompareCmd.java:315)
at com.adobe.granite.indexing.tool.CompareCmd.run(CompareCmd.java:183)
at com.adobe.granite.indexing.tool.Main.main(Main.java:112)
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
Your build is failing because you are trying to deploy an index that has an invalid name (conflict name), please take a look here at how to manage the index names for the cloud.
The log explains clearly:
Can not add a new customized index /oak:index/damAssetLucene-8-custom-1 because an index (possibly merged) named /oak:index/damAssetLucene-9 that has a higher major version already exists. As higher major versions take precedence, the new customized index will not be used. In order to resolve the problem, the new customized index needs to be merged with the latest index, and renamed, so that it has a higher version number than the latest index. Suggested name for new index: /oak:index/damAssetLucene-9-custom-1
Try to update the index's name from oak:index/damAssetLucene-8-custom-1 to: oak:index/damAssetLucene-9-custom-1
Please read more about naming indexes here: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/operations/indexing...
Hi,
Your build is failing because you are trying to deploy an index that has an invalid name (conflict name), please take a look here at how to manage the index names for the cloud.
The log explains clearly:
Can not add a new customized index /oak:index/damAssetLucene-8-custom-1 because an index (possibly merged) named /oak:index/damAssetLucene-9 that has a higher major version already exists. As higher major versions take precedence, the new customized index will not be used. In order to resolve the problem, the new customized index needs to be merged with the latest index, and renamed, so that it has a higher version number than the latest index. Suggested name for new index: /oak:index/damAssetLucene-9-custom-1
Try to update the index's name from oak:index/damAssetLucene-8-custom-1 to: oak:index/damAssetLucene-9-custom-1
Please read more about naming indexes here: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/operations/indexing...