Hi ,
Sorry if i was not clear with my question before .
Limitreads is the attribute name under
JMX Console -> Query Engine Settings .
This attribute is used to set the limit on the number of nodes query can traverse in one go .
Let me put some sample code for reference to my question .
private void processAndPrepareResult(List<String> searchPaths, String uniqueId, String usageLimit, MyDto myDto ) throws RepositoryException {
try
{
if (CollectionUtils.isNotEmpty(searchPaths)) {
Iterator<String> searchPathIterator = searchPaths.iterator();
while (searchPathIterator.hasNext()) {
String searchPath = searchPathIterator.next();
SearchResult result = prepareResults(usageLimit, searchPath, uniqueId);
processMyDto(result, myDto);
searchPathIterator.remove();
}
}
} catch (SupportException ex) {
LOG.debug("Thrown exception caught in processAndPrepareResult() :{}",ex);
String errorPath = ex.getMessage();
List<String> childNodePaths = getChildNodePaths(errorPath);
searchPaths.remove(searchPaths.indexOf(errorPath));
searchPaths.addAll(childNodePaths);
processAndPrepareResult(searchPaths, uniqueId, usageLimit, disclaimerAuditVo);
}
}
private SearchResult prepareResults(String usageLimit, String searchPath, String uniqueId) throws SupportException {
try {
SearchResult result = null;
int usageLimitNumber = Integer.parseInt(usageLimit);
Map<String, String> params = new HashMap<>();
params.put("path", searchPath);
params.put("type", "cq:Page");
params.put("fulltext", "\"[d:" + uniqueId + "]\"");
params.put("fulltext.relPath", "jcr:content");
params.put("p.limit", String.valueOf(usageLimitNumber + 1));
if (builder != null) {
Query query = builder.createQuery(PredicateGroup.create(params), session);
result = query.getResult(); //UnsupportedOperationException will be thrown here for exceeding the node search limit
}
return result;
} catch (UnsupportedOperationException e) {
throw new SupportException(searchPath);
}
}
Let me rephrase my question here with an example scenario .
- In the first run of the query let's assume the search path is "/content" . It throws error because of the number of nodes inside "content" node .
- In the code i will catch that exception and find out the child nodes under "/content" .
- Let's assume that i got "/content/childNode" as a child node and inside this "/content/childNode" we have very few child nodes .
- So in the second run of the query it will try to search under "/content/childNode" which has only few child nodes so it should work fine and return the search result .
- But i am facing some challenge at this point .
- Now it's throwing the same error for "/content/childNode" which it should not throw as the child node has only few further child nodes .
Please let me know if i am missing out on something here or if there something wrong with the code .
Thanks you in advance .
