: With the standard setup, the "OR" operator is used between two or more : search values.
correct, that's because it is the default behavior of the Lucene QueryParser (which is used by the StandardRequestHandler) : How can I setup Solar, that my users don't have to key in AND all the : time? Changing the way the StandardRequestHandler uses the QueryParser currently requires subclassing it -- but I have another suggestion, take a look at the DisMaxRequestHandler... http://wiki.apache.org/solr/DisMaxRequestHandler http://incubator.apache.org/solr/docs/api/org/apache/solr/request/DisMaxRequestHandler.html ...it's designed to accept simple search input from users, and let you control how the innput is processed and searched across various fields using either query params, or init params in the solrconfig.xml. One of those params is "mm" which affects the "minNrShouldMatch" value of BooleanQueries produced by the handler. In the simple case where you want all of the input to be required, you can use a value of "100%" but more complicated expressions are supported for saying "if 3 or less clauses are specified then all are required, more then 3 but up to and including 6 clauses all but one must match, more then 6 clauses 90% must match" (3<-1 6<90%) ... http://incubator.apache.org/solr/docs/api/org/apache/solr/util/doc-files/min-should-match.html -Hoss
