Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 8268 invoked from network); 2 Mar 2010 02:04:44 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Mar 2010 02:04:44 -0000 Received: (qmail 35664 invoked by uid 500); 2 Mar 2010 02:04:39 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 35619 invoked by uid 500); 2 Mar 2010 02:04:39 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 35610 invoked by uid 99); 2 Mar 2010 02:04:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Mar 2010 02:04:39 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [69.147.65.186] (HELO smtp127.sbc.mail.sp1.yahoo.com) (69.147.65.186) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 02 Mar 2010 02:04:33 +0000 Received: (qmail 50184 invoked from network); 2 Mar 2010 02:04:12 -0000 Received: from adsl-69-225-46-239.dsl.skt2ca.pacbell.net (sreichgut@69.225.46.239 with plain) by smtp127.sbc.mail.sp1.yahoo.com with SMTP; 01 Mar 2010 18:04:11 -0800 PST X-Yahoo-SMTP: KVt7LXSswBDb8bcpmoHiWzt8dqE9Kd9VLT9Sh.IspPZrSIn.Yhtxrw-- X-YMail-OSG: Xs2ziW8VM1lQfpds581BEuNK9NyA0ewVWb.RZh7fgJbLKKaYXL.G6EzymeQUwkAdAQdBQhkTxOek1gGGsNWzEjAA84BZ1fwdwBggQEWCo9T1U23ymg1zlZfSj7A3zxmy4OUo8t5FMw3JrijNpmMEywQpoTbN289eGERIvNt.t9hzKcTTTOMCpapmZfD7JK.c7hVABieD6uJjRH_8RbASco90a8OkHCHb_7In.nxdyjpOm2chbdcACsuk.I7IsJelnbcGqFBTUy1H53LMVNY- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4B8C7213.9080104@axtaweb.com> Date: Mon, 01 Mar 2010 18:04:03 -0800 From: Steve Reichgut User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 MIME-Version: 1.0 To: solr-user@lucene.apache.org Subject: Re: Search Result differences Standard vs DisMax References: <4B8C64EA.5050909@axtaweb.com> <4B8C6A38.90101@gmail.com> In-Reply-To: <4B8C6A38.90101@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thanks Joe. That was exactly the issue. When I added 'mm=1', I got exactly the results I was looking for. Where would I change the default value for the 'mm' parameter? Is it in solrconfig.xml? Steve On 3/1/2010 5:30 PM, Joe Calderon wrote: > what are you using for the mm parameter? if you set it to 1 only one > word has to match, > On 03/01/2010 05:07 PM, Steve Reichgut wrote: >> ***Sorry if this was sent twice. I had connection problems here and >> it didn't look like the first time it went out**** >> >> I have been testing out results for some basic queries using both the >> Standard and DisMax query parsers. The results though aren't what I >> expected and am wondering if I am misundertanding how the DisMax >> query parser works. >> >> For example, let's say I am doing a basic search for "Apache Solr" >> across a single field = Field 1 using the Standard parser. My results >> are exactly what I expected. Any document that includes either >> "Apache" or "Solr" or "Apache Solr" in Field 1 is listed with >> priority given to those that include both words. >> >> Now, if I do the same search for "Apache Solr" across multiple fields >> - Field 1, Field 2 - using DisMax, I would expect basically the same >> results. The results should include any document that has one or both >> words in Field 1 or Field 2. >> >> When I run that query in DisMax though, it only returns the documents >> that have BOTH words included which in my sample set only includes 1 >> or 2 documents. I thought that, by default, DisMax should make both >> words optional so I am confused as to why I am only getting such a >> small subset. >> >> Can anyone shed some light on what I am doing wrong or if I am >> misunderstanding how DisMax works. >> >> Thanks, >> Steve > >