QuestionQ5

Adobe Experience Manager Sites Architect Master

A new AEM Sites implementation contains a component that lists the 10 most recently published PDF documents in AEM Assets. The component behaves as expected during development and passes QA testing. The business begins using it while entering content and uploading assets in preparation for go-live. A few days later, the component’s PDF list is empty.

What is the most likely cause of this issue?

Explanation

Oak queries without an appropriate matching index traverse repository nodes to find results. As the number of Assets grows, that traversal can hit Oak’s query read/traversal limit and be stopped, leaving the PDF-list query without results. A suitable Oak index supports the query efficiently at production-scale content volumes.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!