Oak indexing in aem 64 for dam:assetcontent | Community
Skip to main content
Level 9
October 9, 2018
Solved

Oak indexing in aem 64 for dam:assetcontent

  • October 9, 2018
  • 3 replies
  • 2760 views

I was trying to run a query with type - dam:AssetContent and on running it in query builder ui I get the result but I see an error in the error login traversing and that there is no index while I mocked up the dam:asset index under oak:index in aem

property - metadata/cq:tags - throws no error while

property - metadata/customprop - throws traversal error

Custom prop is of type “long”

query

type- dam:AssetContent

path- /content/dam

property - metadata/customprop

property.value - 123

could i be missing something basic ? Please advise

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 Peter_Puzanovs

Hey NitroHazeDev,

Adobe have recorded beautiful Gem on Indexing: Best Practices for Indexing and Queries in AEM Have you seen it(must see)?

By the sound of it, it looks like you are missing index for metadata/customprop.

We also have this brilliant tool that allows to create indexes easily[1]

[1] Oak Utilities : Index Definition Generator

Thank you!

Regards,

Peter

3 replies

Peter_Puzanovs
Community Advisor
Peter_PuzanovsCommunity AdvisorAccepted solution
Community Advisor
October 9, 2018

Hey NitroHazeDev,

Adobe have recorded beautiful Gem on Indexing: Best Practices for Indexing and Queries in AEM Have you seen it(must see)?

By the sound of it, it looks like you are missing index for metadata/customprop.

We also have this brilliant tool that allows to create indexes easily[1]

[1] Oak Utilities : Index Definition Generator

Thank you!

Regards,

Peter

smacdonald2008
Level 10
October 9, 2018

great answer Peter!

Level 9
October 9, 2018

So i did refer to it and created indices based on it but in vain . Then checked Oak Utilities : Index Definition Generator , validated and it looked right as well. I loved the generator url makes life easier

BUT the main part that was incorrect was the "async" that was a misspell.. wonder if i was dozing but yeah , correcting the spelling helped.

Thanks