Hi, Also have a look at mm=0% acting as OR if you end up using dismax: http://wiki.apache.org/solr/ExtendedDisMax#mm_.28Minimum_.27Should.27_Match.29
Otis -- Solr & ElasticSearch Support http://sematext.com/ On Thu, Jan 10, 2013 at 7:47 AM, Erick Erickson <erickerick...@gmail.com>wrote: > No, you're pretty much on track. You can also just include the field > multiple times if you want, itemModelNoExactMatchStr:123-4567 OR > itemMOdelNoExactMatchStr:345-034985 > > But > itemModelNoExactMatchStr:(123-4567 OR 345-034985) works just as well and is > more compact. > > 15 terms is actually quite short by Solr standards, the default cap is 1024 > boolean clauses, which you can change, it's just there to catch > pathalogical (usually machine-generated) huge queries and make sure you > consciously make a decision that it's OK. > > Best > Erick > > > On Wed, Jan 9, 2013 at 4:58 PM, geeky2 <gee...@hotmail.com> wrote: > > > hello, > > > > environment: solr 3.5 > > > > i have a requirement to perform a boolean query (like the example below) > > with a large number of terms. > > > > the number of terms could be 15 or possibly larger. > > > > after looking over several theads and the smiley book - i think i just > have > > include the parens and string all of the terms together with OR's > > > > i just want to make sure that i am not missing anything. > > > > is there a better or more efficient way of doing this? > > > > http://server:port > > > /dir/core1/select?qt=modelItemNoSearch&q=itemModelNoExactMatchStr:%285-100-NGRT7%20OR%205-10-10MS7%20OR%20404%29&rows=30&debugQuery=on&rows=40 > > > > > > thx > > mark > > > > > > > > > > -- > > View this message in context: > > > http://lucene.472066.n3.nabble.com/performing-a-boolean-query-OR-with-a-large-number-of-terms-tp4032039.html > > Sent from the Solr - User mailing list archive at Nabble.com. > > >
