FAQ
Hi All,



We have a requirement where in we need to construct a BooleanQuery, with
the TermQueries, whose count is large , but that it is somewhat fixed
number. It could be around a 5000 or 6000.



At present we are hitting the BooleanQuery.TooManyClauses exception, as
the default count of max caluse is 1024.



I just wanted to know if there are any performance related impact
because of setting this to some high value, using
BooleanQuery.setMaxClauseCount();



Please help.



Details.

Lucene Version = 2.4.0









Regards,

Raghav

Search Discussions

  • Raghavendra D.V Rao (rarao2) at Dec 8, 2010 at 1:20 pm
    Update on my previous query.



    In our application environment, our queries will typically contain
    200-300 clauses. The chances of clauses becoming 5000 is less.



    Hence we are interested in knowing the actual impact of setting the
    setMaxClauseCount () to high value on the normal queries, containing
    less number of clauses.



    Regards,

    Raghav



    From: Raghavendra D.V Rao (rarao2)
    Sent: Wednesday, December 08, 2010 10:36 AM
    To: 'java-user@lucene.apache.org'; 'lucene-net-user@lucene.apache.org'
    Cc: Preetham Kajekar (preetham)
    Subject: Problem with "BooleanQuery.TooManyClauses"



    Hi All,



    We have a requirement where in we need to construct a BooleanQuery, with
    the TermQueries, whose count is large , but that it is somewhat fixed
    number. It could be around a 5000 or 6000.



    At present we are hitting the BooleanQuery.TooManyClauses exception, as
    the default count of max caluse is 1024.



    I just wanted to know if there are any performance related impact
    because of setting this to some high value, using
    BooleanQuery.setMaxClauseCount();



    Please help.



    Details.

    Lucene Version = 2.4.0









    Regards,

    Raghav
  • Ian Lea at Dec 8, 2010 at 1:41 pm
    Setting it to a high value shouldn't have any noticeable effect on the
    normal queries. And since your high values aren't very high I'd
    expect them to be fine too. Try it and see.

    btw 2.4.0 is ancient.


    --
    Ian.


    On Wed, Dec 8, 2010 at 7:05 AM, Raghavendra D.V Rao (rarao2)
    wrote:
    Update on my previous query.



    In our application environment, our queries will typically contain
    200-300 clauses. The chances of  clauses becoming 5000  is less.



    Hence we are interested in knowing the actual impact of setting the
    setMaxClauseCount () to high value on the normal queries, containing
    less number of clauses.



    Regards,

    Raghav



    From: Raghavendra D.V Rao (rarao2)
    Sent: Wednesday, December 08, 2010 10:36 AM
    To: 'java-user@lucene.apache.org'; 'lucene-net-user@lucene.apache.org'
    Cc: Preetham Kajekar (preetham)
    Subject: Problem with "BooleanQuery.TooManyClauses"



    Hi All,



    We have a requirement where in we need to construct a BooleanQuery, with
    the TermQueries, whose count is large , but that it is somewhat fixed
    number.  It could be around a 5000 or 6000.



    At present we are hitting the BooleanQuery.TooManyClauses exception, as
    the  default count of max caluse is 1024.



    I just wanted to know if there are any performance related impact
    because of setting this to some high value, using
    BooleanQuery.setMaxClauseCount();



    Please help.



    Details.

    Lucene Version = 2.4.0









    Regards,

    Raghav


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupjava-user @
categorieslucene
postedDec 8, '10 at 1:20p
activeDec 8, '10 at 1:41p
posts3
users2
websitelucene.apache.org

People

Translate

site design / logo © 2022 Grokbase