Hi All,
I have created custom Lucene index and it works fine in local but when I try deploy the same to Cloud, this new index impacting other queries where they use cq:tags.
<lucene-0-custom-2
jcr:primaryType="oak:QueryIndexDefinition"
async="[async,nrt]"
compatVersion="{Long}2"
evaluatePathRestrictions="{Boolean}true"
includedPaths="[/content/dam/mch/train-center/en]"
queryPaths="[/content/dam/mch/train-center/en]"
maxFieldLength="{Long}100000"
reindexCount="{Long}6"
type="lucene">
<indexRules jcr:primaryType="nt:unstructured">
<nt:unstructured
jcr:primaryType="nt:unstructured"
indexNodeName="{Boolean}true">
<properties jcr:primaryType="nt:unstructured">
<dcTitle
jcr:primaryType="nt:unstructured"
boost="{Double}2.0"
name="jcr:content/metadata/dc:title"
nodeScopeIndex="{Boolean}true"
ordered="{Boolean}true"
propertyIndex="{Boolean}true"
useInSpellcheck="{Boolean}true"
useInSuggest="{Boolean}true"/>
</properties>
</nt:unstructured>
</indexRules>
</lucene-0-custom-2>
When I try to delete the index from Cloud environment, type property setting as a "disabled" and not removing from Cloud environment.
I followed this steps to delete index but no luck
https://www.initialyze.com/insights/how-to-deploy-custom-oak-indexes-in-aem-as-a-cloud-services
Could you please help me how to delete custom index from AEM Cloud environment.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @RR_MR
Please check https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/index...
The following only applies to custom indexes. Product indexes may not be removed as they are used by AEM.
A customized index may be removed in a later version of the customer application, by removing it from the customer repository. An index which is removed from the repository is not used for queries in AEM although it might still be present in the instances for a while. There is a clean-up mechanism in place that runs periodically which cleans up older versions of indexes from the instances.
There is a acs-commons tool for managing oak index. Can check that also.
https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-oak-index/index.html
@RR_MR Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
As suggested by @arunpatidar , I followed the below article
but no luck, custom index still exist with "type=disabled" property and not able to remove.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies