You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by François Cassistat <f....@maya-systems.com> on 2011/01/27 18:48:23 UTC
Query limits
Hi list,
we are planning to make queries with a lot of property tests and boolean operators.
Is there a theoretical and practical limit to the size of the request?
Could there be some serious slow-down if the query is too big?
I'm currently using XPath, but I could use something else.
Thanks,
François
Re: AW: AW: Query limits
Posted by Alexander Klimetschek <ak...@adobe.com>.
On 28.01.11 17:27, "François Cassistat" <f....@maya-systems.com>
wrote:
>Thanks Jukka, it is great news !
>
>1024 should be okay for now. But maybe we should send a ticket into Jira
>about the org.apache.lucene.maxClauseCount issue (maybe it was already
>opened?).
If it doesn't work, it is probably a Lucene issue.
http://lucene.apache.org/java/1_4_3/systemproperties.html
Regards,
Alex
--
Alexander Klimetschek
Developer // Adobe (Day) // Berlin - Basel
Re: AW: AW: Query limits
Posted by François Cassistat <f....@maya-systems.com>.
Thanks Jukka, it is great news !
1024 should be okay for now. But maybe we should send a ticket into Jira about the org.apache.lucene.maxClauseCount issue (maybe it was already opened?).
Thank you,
François
Le 2011-01-28 à 9:37 AM, Cech. Ulrich a écrit :
> Hallo Alexander,
>
> this does not work either.
> I think, we have to wait until this issue is fixed.
>
> Thanks,
> Ulrich
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alexander Klimetschek [mailto:aklimets@adobe.com]
> Gesendet: Freitag, 28. Januar 2011 15:15
> An: users@jackrabbit.apache.org
> Betreff: Re: AW: Query limits
>
> On 28.01.11 14:54, "Cech. Ulrich" <Ul...@aeb.de> wrote:
>> is there another hint for increasing the maxClauseCount value? I set the
>> system property, but the error still occurs with a value of 1024,
>> although I set it to "Integer.MAX_VALUE".
>
> I guess you will need to set the value on startup, e.g. using
> -Dorg.apache.lucene.maxClauseCount=999999 on the command line.
>
> Regards,
> Alex
>
> --
> Alexander Klimetschek
> Developer // Adobe (Day) // Berlin - Basel
>
>
>
>
AW: AW: Query limits
Posted by "Cech. Ulrich" <Ul...@aeb.de>.
Hallo Alexander,
this does not work either.
I think, we have to wait until this issue is fixed.
Thanks,
Ulrich
-----Ursprüngliche Nachricht-----
Von: Alexander Klimetschek [mailto:aklimets@adobe.com]
Gesendet: Freitag, 28. Januar 2011 15:15
An: users@jackrabbit.apache.org
Betreff: Re: AW: Query limits
On 28.01.11 14:54, "Cech. Ulrich" <Ul...@aeb.de> wrote:
>is there another hint for increasing the maxClauseCount value? I set the
>system property, but the error still occurs with a value of 1024,
>although I set it to "Integer.MAX_VALUE".
I guess you will need to set the value on startup, e.g. using
-Dorg.apache.lucene.maxClauseCount=999999 on the command line.
Regards,
Alex
--
Alexander Klimetschek
Developer // Adobe (Day) // Berlin - Basel
Re: AW: Query limits
Posted by Alexander Klimetschek <ak...@adobe.com>.
On 28.01.11 14:54, "Cech. Ulrich" <Ul...@aeb.de> wrote:
>is there another hint for increasing the maxClauseCount value? I set the
>system property, but the error still occurs with a value of 1024,
>although I set it to "Integer.MAX_VALUE".
I guess you will need to set the value on startup, e.g. using
-Dorg.apache.lucene.maxClauseCount=999999 on the command line.
Regards,
Alex
--
Alexander Klimetschek
Developer // Adobe (Day) // Berlin - Basel
AW: Query limits
Posted by "Cech. Ulrich" <Ul...@aeb.de>.
Hi Jukka,
is there another hint for increasing the maxClauseCount value? I set the system property, but the error still occurs with a value of 1024, although I set it to "Integer.MAX_VALUE".
Thanks in advance,
Ulrich
-----Ursprüngliche Nachricht-----
Von: Jukka Zitting [mailto:jzitting@adobe.com]
Gesendet: Freitag, 28. Januar 2011 11:02
An: users@jackrabbit.apache.org
Betreff: Re: Query limits
Hi,
On 27.01.2011 18:48, François Cassistat wrote:
> we are planning to make queries with a lot of property tests and
> boolean operators. Is there a theoretical and practical limit to the
> size of the request?
Jackrabbit executes queries against the Lucene query index it maintains
for each workspace. The maximum number of clauses in a Lucene query is
limited to 1024 by default, but you can increase that if needed by
setting the "org.apache.lucene.maxClauseCount" system property. Even a
few hundred constraints in an XPath query should still be fine with the
default settings.
> Could there be some serious slow-down if the query is too big?
Not really. The (non-join) query execution time is much more dominated
by your content structure, distribution of search terms, the kind of
constraints you use and the number of results you expect from the query.
--
Jukka Zitting
Re: Query limits
Posted by Jukka Zitting <jz...@adobe.com>.
Hi,
On 27.01.2011 18:48, François Cassistat wrote:
> we are planning to make queries with a lot of property tests and
> boolean operators. Is there a theoretical and practical limit to the
> size of the request?
Jackrabbit executes queries against the Lucene query index it maintains
for each workspace. The maximum number of clauses in a Lucene query is
limited to 1024 by default, but you can increase that if needed by
setting the "org.apache.lucene.maxClauseCount" system property. Even a
few hundred constraints in an XPath query should still be fine with the
default settings.
> Could there be some serious slow-down if the query is too big?
Not really. The (non-join) query execution time is much more dominated
by your content structure, distribution of search terms, the kind of
constraints you use and the number of results you expect from the query.
--
Jukka Zitting