Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7B8FF11FAC for ; Fri, 18 Apr 2014 20:18:24 +0000 (UTC) Received: (qmail 48860 invoked by uid 500); 18 Apr 2014 20:18:20 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 48766 invoked by uid 500); 18 Apr 2014 20:18:19 -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 48758 invoked by uid 99); 18 Apr 2014 20:18:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Apr 2014 20:18:19 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of a.lakshmi458@gmail.com designates 209.85.223.182 as permitted sender) Received: from [209.85.223.182] (HELO mail-ie0-f182.google.com) (209.85.223.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Apr 2014 20:18:15 +0000 Received: by mail-ie0-f182.google.com with SMTP id y20so1980981ier.13 for ; Fri, 18 Apr 2014 13:17:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=3W79gGl/RSms7lKf428xLCPwkRrB8eH24omfZXal/Fc=; b=uEnRRnE7zD6AFAo5+QyD9P4IRWtFzYIcQQxMwbECamOq5AWqEpOrAvUnnN7ePfo8se r+JInrWJlKhYlqApmeWnMtB1FprFBC4eqyKB9OUufQa0YMTQJ6PqyTdB8y7zf8nbvYcc +lJPHBS54vHLGI3s5Jguotiy/WU+Md3Ks2KnDjeYQusvfjb05kemManAfnzxn1M9Mjcr My7HqPv8tGC2mzejVO61UFipKOd3O4dird5I6rksJ7A7kbFs/B8WQXyvVM0L+L8PTQjb tPRgIBytS2ZKQT5lCe2vnOuPknf4RwHhaxikVUYxZk2f/YIEWXeSBdbDlog8MUkRaCj9 NLVw== X-Received: by 10.50.138.72 with SMTP id qo8mr6326813igb.26.1397852272851; Fri, 18 Apr 2014 13:17:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.228.195 with HTTP; Fri, 18 Apr 2014 13:17:32 -0700 (PDT) In-Reply-To: References: <97xc72696f3x08gy5x75nfsj.1397850930318@email.android.com> From: A Laxmi Date: Fri, 18 Apr 2014 16:17:32 -0400 Message-ID: Subject: Re: Boost Search results To: solr-user@lucene.apache.org, Markus Jelsma Content-Type: multipart/alternative; boundary=001a1134c7922bff6504f756d814 X-Virus-Checked: Checked by ClamAV on apache.org --001a1134c7922bff6504f756d814 Content-Type: text/plain; charset=UTF-8 Markus, like I mentioned in my last email, I have got the qf with title, content and url. That doesn't help a whole lot. Could you please advise if there are any other parameters that I should consider for solr request handler config or the numbers I have got for title, content, url in qf parameter have to be modified? Thanks for your help.. On Fri, Apr 18, 2014 at 4:08 PM, A Laxmi wrote: > Hi Markus, Yes, you are right. I passed the qf from my front-end framework > (PHP which uses SolrClient). This is how I got it set-up: > > $this->solr->set_param('defType','edismax'); > $this->solr->set_param('qf','title^10 content^5 url^5'); > > where you can see qf = title^10 content^5 url^5 > > > > > > > On Fri, Apr 18, 2014 at 4:02 PM, Markus Jelsma > wrote: > >> Hi, replicating full features search engine behaviour is not going to >> work with nutch and solr out of the box. You are missing a thousand >> features such as proper main content extraction, deduplication, >> classification of content and hub or link pages, and much more. These >> things are possible to implement but you may want to start with having you >> solr request handler better configured, to begin with, your qf parameter >> does not have nutchs default title and content field selected. >> >> >> A Laxmi schreef:Hi, >> >> >> When I started to compare the search results with the two options below, I >> see a lot of difference in the search results esp. the* urls that show up >> on the top *(*Relevancy *perspective). >> >> (1) Nutch 2.2.1 (with *Solr 4.0*) >> (2) Bing custom search set-up >> >> I wonder how should I tweak the boost parameters to get the best results >> on >> the top like how Bing, Google does. >> >> Please suggest why I see a difference and what parameters are best to >> configure in Solr to achieve what I see from Bing, or Google search >> relevancy. >> >> Here is what i got in solrconfig.xml: >> >> edismax >> >> text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4 >> >> *:* >> 10 >> *,score >> >> >> Thanks >> > > --001a1134c7922bff6504f756d814--