jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-2785) Add QueryEngine.executeQuery without limit and offset
Date Tue, 11 Aug 2015 12:20:46 GMT

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

Thomas Mueller updated OAK-2785:
    Fix Version/s:     (was: 1.3.5)

> Add QueryEngine.executeQuery without limit and offset
> -----------------------------------------------------
>                 Key: OAK-2785
>                 URL: https://issues.apache.org/jira/browse/OAK-2785
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, query
>            Reporter: angela
>            Assignee: Thomas Mueller
>              Labels: technical_debt
>             Fix For: 1.3.4
> looking at queries executed in oak it seems that the vast majority doesn't set neither
limit nor offset. Since there are not public constants available for NO_LIMIT and NO_OFFSET
the corresponding values (i.e. Long.MAX_VALUE and 0 respectively) are repeatedly used. 
> since i found that i always have to look up how to indicated the NO_LIMIT, i would like
to suggest that we either introduce constants for the 2 parameters or provide another {{executeQuery}}
method that doesn't require to specify limit and offset (-> the constants might be kept
private in this case).
> discussing with [~tmueller] it seemed that he would rather prefer the second approach.
> in any case it would allow us to make the various usages of {{QueryEngine.executeQuery}}
more readable

This message was sent by Atlassian JIRA

View raw message