Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-2830

JCR-SQL2 : Query on large node-set is (too) slow even when offset and limit is used

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.3
    • None
    • query
    • None
    • + Win7 (64bit)
      + JR built from latest greatest sources
      + repo with many nodes of same node type > 77'000

    Description

      Given a node-set of approx 77'000 entries a SQL2-query limited to 10 nodes takes approx 37 to 59sec whereas the corresponding SQL returns in less than 1sec.

      Query q = session.getWorkspace().getQueryManager().createQuery( "select * from [task]", Query.SQL2 );
      q.setOffset( 0 ); // or any other offset
      q.setLimit( 10 );
      returnValue = q.execute();

      Attachments

        1. JCR-2830.patch
          18 kB
          Alex Deparvu

        Issue Links

          is blocked by

          Improvement - An improvement or enhancement to an existing feature or task. JCR-2959 SQL2 QueryEngine should use Lucene for sort

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. JCR-3446 Implement sort by node name for XPATH

          • Major - Major loss of function.
          • Open

          Activity

            People

              Unassigned Unassigned
              clemensdev Clemens Wyss
              Votes:
              4 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: