Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Tue, 21 May 2013 07:53:25 +0000 (UTC)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12601342.1343988487321.351749.1369122805270@arcas>
In-Reply-To: <JIRA.12601342.1343988487321@arcas>
References: <JIRA.12601342.1343988487321@arcas>
Subject: [jira] [Updated] (JCR-3402) getSize() returning too many often -1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/JCR-3402?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-3402:
-------------------------------

    Fix Version/s: 2.6.2
   =20
> getSize() returning too many often -1
> -------------------------------------
>
>                 Key: JCR-3402
>                 URL: https://issues.apache.org/jira/browse/JCR-3402
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>            Reporter: C=C3=A9dric Damioli
>            Assignee: C=C3=A9dric Damioli
>             Fix For: 2.6.2, 2.7
>
>         Attachments: QueryResultImpl.patch
>
>
> I've came accross the well known behaviour of query results returning -1 =
when asked for getSize().
> While this is ok for optimization reasons (lazy results fetching), I just=
 discovered that the default "resultFetchSize" value in lucene queries is I=
nteger.MAX_VALUE, so in all queries I've ever executed, all results were ac=
tually fetched before asking for getSize, so IMHO nothing prevents getSize(=
) to return the real value instead -1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira