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

Cédric Damioli updated JCR-3402:
--------------------------------

    Fix Version/s: 2.6

As asked on the dev ML, I set this as fixed for 2.6 for discussing potential 
integration

I use this patch in production since one year without problems, but I certainly 
don't cover all JCR areas (especially, I don't use ACL which may impact query 
results).

Unit tests pass well with this patch included
                
> 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édric Damioli
>             Fix For: 2.6
>
>         Attachments: QueryResultImpl.java.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 
> Integer.MAX_VALUE, so in all queries I've ever executed, all results were 
> actually 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 administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to