Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

Unable to filter assets based on 'folders' option

Avatar

Level 2

Our authors want to filter the DAM based on path, type of file (file or folder)
Currently we have DAM folder under /content/dam where 'loose assets' and 'folders' exist together (I'm assuming that's a normal) under any given path. But with AEM's OOTB filter option in DAM, we can't seem to filter folders. 
- I go to filter under dam 

udayashankarc29_0-1701192249971.png

- then there are 3 options under path - files, folders, files & folder : 

udayashankarc29_1-1701192329023.png

 

Ónly 'Files' filter work and the other two doesn't seem to work. When I try to filter with 'Folders' - I see empty results, but we have loads of folders. Then I did the same in a 'vanilla' instance - plain 6.5 without any of our content and code, even there I see this problem : 

udayashankarc29_2-1701192586287.png


Is this a known issue ? Are we doin something wrong?

Upon checking errors - One commons trace in my vanilla instance as well as my equipped instance - is this : 

28.11.2023 22:28:58.224 *WARN* [[0:0:0:0:0:0:0:1] [1701190738137] GET /mnt/overlay/granite/ui/content/shell/omnisearch/searchresults.html HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.lucene.util.FacetHelper facets for jcr:content/metadata/dam:status not yet indexed: java.lang.IllegalArgumentException: field "jcr:content/metadata/dam:status_facet" was not indexed with SortedSetDocValues
28.11.2023 22:28:58.225 *WARN* [[0:0:0:0:0:0:0:1] [1701190738137] GET /mnt/overlay/granite/ui/content/shell/omnisearch/searchresults.html HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.lucene.util.FacetHelper facets for jcr:content/metadata/dam:status not yet indexed: java.lang.IllegalArgumentException: field "jcr:content/metadata/dam:status_facet" was not indexed with SortedSetDocValues
28.11.2023 22:28:58.294 *INFO* [Apache Sling Resource Resolver Finalizer Thread] com.adobe.granite.repository Service [23657, [org.apache.jackrabbit.oak.api.jmx.SessionMBean]] ServiceEvent UNREGISTERING
28.11.2023 22:28:58.399 *WARN* [[0:0:0:0:0:0:0:1] [1701190738137] GET /mnt/overlay/granite/ui/content/shell/omnisearch/searchresults.html HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.lucene.util.FacetHelper facets for jcr:content/metadata/dam:status not yet indexed: java.lang.IllegalArgumentException: field "jcr:content/metadata/dam:status_facet" was not indexed with SortedSetDocValues
28.11.2023 22:28:58.400 *WARN* [[0:0:0:0:0:0:0:1] [1701190738137] GET /mnt/overlay/granite/ui/content/shell/omnisearch/searchresults.html HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.lucene.util.FacetHelper facets for jcr:content/metadata/dam:status not yet indexed: java.lang.IllegalArgumentException: field "jcr:content/metadata/dam:status_facet" was not indexed with SortedSetDocValues
28.11.2023 22:28:58.838 *WARN* [[0:0:0:0:0:0:0:1] [1701190738834] GET /mnt/overlay/granite/ui/content/shell/omnisearch/searchresults/singleresults/views/card.20.5.5.html HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.lucene.util.FacetHelper facets for jcr:content/metadata/dam:status not yet indexed: java.lang.IllegalArgumentException: field "jcr:content/metadata/dam:status_facet" was not indexed with SortedSetDocValues


Need some help on this 


1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@udayashankarc29 

 

I can reproduce the same issue on AEM SP 15 as well. It seems like a product bug to me. Please raise a Adobe Support ticket as the issue can be reproduced in vanilla instance as well.

 

As you mentioned, the indexing error logs are showing up on selection of any option from the dropdown(Files, Folders, Files & Folders).

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

@udayashankarc29 

 

I can reproduce the same issue on AEM SP 15 as well. It seems like a product bug to me. Please raise a Adobe Support ticket as the issue can be reproduced in vanilla instance as well.

 

As you mentioned, the indexing error logs are showing up on selection of any option from the dropdown(Files, Folders, Files & Folders).