After created custom oak index for the DAM assets in AEM clooud. Asset search and asset side panel are not working | Community
Skip to main content
Nilesh_Mali
Nilesh_Mali
Level 3
August 4, 2023
Solved

After created custom oak index for the DAM assets in AEM clooud. Asset search and asset side panel are not working

  • August 4, 2023
  • 1 reply
  • 747 views

After created custom oak index for the DAM assets in AEM clooud. Asset search and asset side panel are not working

Found below errors in the logs

 

*WARN* [IP [NUmberID] GET /mnt/overlay/granite/ui/content/shell/omnisearch/searchresults.html HTTP/1.1] org.apache.jackrabbit.oak.query.QueryImpl Potentially improper use of index /oak:index/pathReference with queryFilterRegex (["']|^)/ to search for value 'rep:facet(jcr:content/metadata/dc:format)'
DateTime [aem-author] 

*WARN* [IP [NUmberID] GET /mnt/overlay/granite/ui/content/shell/omnisearch/searchresults.html HTTP/1.1] org.apache.jackrabbit.oak.query.QueryImpl Potentially improper use of index /oak:index/pathReference with queryFilterRegex (["']|^)/ to search for value 'rep:facet(jcr:content/metadata/dam:status)'

*WARN* [IP [NUmberID] GET /mnt/overlay/granite/ui/content/shell/omnisearch/searchresults.html HTTP/1.1] org.apache.jackrabbit.oak.query.QueryImpl Potentially improper use of index /oak:index/pathReference with queryFilterRegex (["']|^)/ to search for value '"imageName"'

 

Using below code to create a custom oak index

 

<damAssetLucene-8-custom-1 jcr:primaryType="oak:QueryIndexDefinition" async="[async,nrt]" compatVersion="{Long}2" evaluatePathRestrictions="{Boolean}true" includedPaths="/content/dam/damPath" reindex="{Boolean}false" reindexCount="{Long}3" seed="{Long}7895649870935705082" tags="[visualSimilaritySearch]" type="lucene"> <aggregates jcr:primaryType="nt:unstructured"> <dam:Asset jcr:primaryType="nt:unstructured"> <include0 jcr:primaryType="nt:unstructured" path="jcr:content"/> <include1 jcr:primaryType="nt:unstructured" path="jcr:content/metadata"/> <include2 jcr:primaryType="nt:unstructured" path="jcr:content/metadata/*"/> </dam:Asset> </aggregates> <facets jcr:primaryType="nt:unstructured" secure="statistical" topChildren="100"/> <indexRules jcr:primaryType="nt:unstructured"> <dam:Asset jcr:primaryType="nt:unstructured"> <properties jcr:primaryType="nt:unstructured"> <format name="jcr:content/metadata/dc:format" propertyIndex="{Boolean}true" jcr:primaryType="nt:unstructured"/> </properties> </dam:Asset> </indexRules> <tika jcr:primaryType="nt:unstructured"> <config.xml jcr:primaryType="nt:file" > <jcr:content jcr:primaryType="nt:unstructured" /> </config.xml> </tika> </damAssetLucene-8-custom-1>

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by aanchal-sikka

Hello @nilesh_mali 

 

This looks like an incomplete index.

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/operations/indexing.html?lang=en#preparing-the-new-index-definition 

If customizing an out-of-the-box index, for example damAssetLucene-8, please copy the latest out-of-the-box index definition from a Cloud Service environment using the CRX DE Package Manager (/crx/packmgr/) . Rename it to damAssetLucene-8-custom-1 (or higher), and add your customizations inside the XML file. This ensures that the required configurations are not being removed inadvertently. For example, the tika node under /oak:index/damAssetLucene-8/tika is required in the customized index of the cloud service. It doesn’t exist on the Cloud SDK.

1 reply

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity AdvisorAccepted solution
Community Advisor
August 4, 2023

Hello @nilesh_mali 

 

This looks like an incomplete index.

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/operations/indexing.html?lang=en#preparing-the-new-index-definition 

If customizing an out-of-the-box index, for example damAssetLucene-8, please copy the latest out-of-the-box index definition from a Cloud Service environment using the CRX DE Package Manager (/crx/packmgr/) . Rename it to damAssetLucene-8-custom-1 (or higher), and add your customizations inside the XML file. This ensures that the required configurations are not being removed inadvertently. For example, the tika node under /oak:index/damAssetLucene-8/tika is required in the customized index of the cloud service. It doesn’t exist on the Cloud SDK.

Aanchal Sikka
    Terms & ConditionsAccessibility statement

    Loading footer...