In this situation, we can: 1. define the oak index for a query 2. try to redesign taxonomy of a repository or structure if it might be improved 3. update oak indexes to cover the query 4. use oak:Unstructured instead of nt:unstructured and sling:Folder instead of sling:OrderedFolder in a case where an order is not required During the development, if we want to skip this error for a while we can increase LimitReads and LimitInMemory parameters for OAK Query Engine: 1. navigate to QueryEngineSettings 2. increase selected parameters 3. this is for development stage only, please, do not push this on production
Please use this thread to ask the related questions.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes