DevOps & Infrastructure
Tuning Oak Query Indexes
AEM Cloud Service expert skill — check a JCR/Oak query is actually served by an index and, when it is not, propose the property/Lucene index-definition change so the query is answered by the index instead of in-memory filtering or sorting. Use for \"query is slow\", \"traversal warning\", \"is my query indexed\", \"tune oak index\", or a scan that flags a JCR/QueryBuilder query. The analyzer locates every query-construction site (createQuery, getQueryManager, Sling findResources / queryResources, PredicateGroup.create / new PredicateGroup); the recipe assesses each flagged query against the supplied index definition(s). Resolution is user-supplied: the index definition(s) are required input — if none is provided the whole pattern is deferred, never guessed. Guided fix — the developer reviews and applies the proposed index change; never auto-apply.
- Publisher / source
- adobe/skills (found on skills.sh)
- Upstream record
- adobe/skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication
- Content fingerprint
800bd49667a62f9d733f4437808ca8caa543efc4145377a78ebc0ce60855d259