Having problem with Query builder when we have more records | Community
Skip to main content
Umamaheswari_Yakkala
Community Advisor
Umamaheswari_YakkalaCommunity Advisor
Community Advisor
September 18, 2019
Solved

Having problem with Query builder when we have more records

  • September 18, 2019
  • 3 replies
  • 4179 views

Having problems with the querybuilder.

We have our own dashboards for the clients. The data comes into these dashboards based on properties defined in the nodes.

To display these dashboards we are using querybuilder api to get the data but recently seeing so many issues like reached 10000 stopping the process etc.

Is there any way that we can optimize the queries or best way to retrieve the data without this msg. That would be great.

Thanks in Advance.

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 Ravi_Pampana

Hi,

You can update the below configuration

In memory read limit property can be increase to your needs.

But note this is impact the performance of the server and you should be adding proper indexing for the properties, so that performance wont be effected.

Hope this helps !

3 replies

U
Adobe Employee
user05162Adobe Employee
Adobe Employee
September 18, 2019

As a short term solution, you can change the "LimitReads" at [3] to a higher number.

For long term:

- First, try to find the query that is getting triggered by setting up a DEBUG logger on the following classes:

  • org.apache.jackrabbit.oak.plugins.index
  • org.apache.jackrabbit.oak.query
  • com.day.cq.search

Then use the explain query[1] tool to find the index that query is using. Then try to optimize the index Or create a new index if its a traversal query. You can use the oakutils[2] tool for index definition.

[1] http://<host>:<port>/libs/granite/operations/content/diagnosistools/queryPerformance.html​

[2] Oak Utilities : Index Definition Generator​

[3] http://<host>:<port>/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dsettings%2Ctype%3DQueryEngineSettings

    S
    Adobe Employee
    sdangAdobe Employee
    Adobe Employee
    September 18, 2019

    Have you considering using the parameter "p.limit" as described here [1].

    [1] Query Builder API

      Ravi_Pampana
      Community Advisor
      Ravi_PampanaCommunity AdvisorAccepted solution
      Community Advisor
      September 18, 2019

      Hi,

      You can update the below configuration

      In memory read limit property can be increase to your needs.

      But note this is impact the performance of the server and you should be adding proper indexing for the properties, so that performance wont be effected.

      Hope this helps !

        Terms & ConditionsAccessibility statement

        Loading footer...