Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <28227677.91591291373592428.JavaMail.jira@thor>
Date: Fri, 3 Dec 2010 05:53:12 -0500 (EST)
From: "Clemens Wyss (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Created: (JCR-2830) JCR-SQL2 : Query on large node-set is
 (too) slow even when offset and limit is used
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

                 Key: JCR-2830
                 URL: https://issues.apache.org/jira/browse/JCR-2830
             Project: Jackrabbit Content Repository
          Issue Type: Improvement
    Affects Versions: 2.3.0
         Environment: + Win7 (64bit)
+ JR built from latest greatest sources
+ repo with many nodes of same node type > 77'000
            Reporter: Clemens Wyss


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();

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.