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 ABE7E10D21 for ; Wed, 27 Nov 2013 16:52:27 +0000 (UTC) Received: (qmail 47773 invoked by uid 500); 27 Nov 2013 16:50:32 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 47694 invoked by uid 500); 27 Nov 2013 16:50:30 -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 47564 invoked by uid 99); 27 Nov 2013 16:50:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Nov 2013 16:50:25 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of SRS0=LcK474=VE=basetechnology.com=jack@yourhostingaccount.com designates 65.254.254.74 as permitted sender) Received: from [65.254.254.74] (HELO mailout03.yourhostingaccount.com) (65.254.254.74) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Nov 2013 16:50:18 +0000 Received: from mailscan12.yourhostingaccount.com ([10.1.15.12] helo=mailscan12.yourhostingaccount.com) by mailout03.yourhostingaccount.com with esmtp (Exim) id 1VliJI-0007y6-Ut for solr-user@lucene.apache.org; Wed, 27 Nov 2013 11:49:56 -0500 Received: from impout01.yourhostingaccount.com ([10.1.55.1] helo=impout01.yourhostingaccount.com) by mailscan12.yourhostingaccount.com with esmtp (Exim) id 1VliJI-0001Q2-TD for solr-user@lucene.apache.org; Wed, 27 Nov 2013 11:49:56 -0500 Received: from authsmtp05.yourhostingaccount.com ([10.1.18.5]) by impout01.yourhostingaccount.com with NO UCE id ugpu1m00R06ZpSa01gpuj2; Wed, 27 Nov 2013 11:49:54 -0500 X-Authority-Analysis: v=2.0 cv=Sc11h4tu c=1 sm=1 a=UdCbmyego4VUa/xJBgcoFg==:17 a=aQzbgH187woA:10 a=Yy1p2O2g_NAA:10 a=3jZET7lWBKwA:10 a=8nJEP1OIZ-IA:10 a=jvYhGVW7AAAA:8 a=KAIgsGObmwYA:10 a=mV9VRH-2AAAA:8 a=NL4621mGOAYXZwismTAA:9 a=wPNLvfGTeEIA:10 a=EMlJoiak7gQA:10 a=9O1N9SI/4ZbXZMy1Cl+5fA==:117 X-EN-OrigOutIP: 10.1.18.5 X-EN-IMPSID: ugpu1m00R06ZpSa01gpuj2 Received: from 207-237-114-232.c3-0.nyr-ubr1.nyr.ny.cable.rcn.com ([207.237.114.232]:52104 helo=JackKrupansky) by authsmtp05.yourhostingaccount.com with esmtpa (Exim) id 1VliJG-0001Er-3V for solr-user@lucene.apache.org; Wed, 27 Nov 2013 11:49:54 -0500 Message-ID: From: "Jack Krupansky" To: References: In-Reply-To: Subject: Re: Term Vector Component Question Date: Wed, 27 Nov 2013 11:49:51 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3555.308 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308 X-EN-UserInfo: e0a4b55451ed9f27313ebf02e3d4348d:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: jack@basetechnology.com Sender: "Jack Krupansky" X-EN-OrigIP: 207.237.114.232 X-EN-OrigHost: 207-237-114-232.c3-0.nyr-ubr1.nyr.ny.cable.rcn.com X-Virus-Checked: Checked by ClamAV on apache.org There is an XML version of explain as well, if parsing the structured text is too difficult for your application. The point is that debug "explain" details precisely the term vector values for actual query terms. Don't let the "debug" moniker throw you - this parameter is simply giving you access to detail information that you might find of value in your application. As Erick explained, the function query approach ("tf(query-term)") also works, kind of, sort of, at least where all query terms must be matched, but when the "OR" operator is used, it won't tell you which term matched - although a tf value of 0 basically tells you that. -- Jack Krupansky -----Original Message----- From: Jamie Johnson Sent: Wednesday, November 27, 2013 11:38 AM To: solr-user@lucene.apache.org Subject: Re: Term Vector Component Question Jack, I'm not following, are you suggesting to turn on debug and then parse the explain? Seems very round about if that is the case, no? On Wed, Nov 27, 2013 at 9:40 AM, Jack Krupansky wrote: > That information would be included in the debugQuery output as well. > > -- Jack Krupansky > > -----Original Message----- From: Jamie Johnson Sent: Wednesday, November > 27, 2013 9:32 AM To: solr-user@lucene.apache.org Subject: Term Vector > Component Question > I am interested in retrieving the tf for terms that matched the query, not > all terms in the document. Is this possible? Looking at the example when > I search for the word cable I get the response that is shown below, > ideally > I'd like to see only the tf for the word cable. Is this possible or would > I need to write a custom query component to do this? > > > > > > 0 > > 2 > > > > > > > > > > 32MB SD card, USB cable, AV cable, battery > > > > > > USB cable > > > > > > earbud headphones, USB cable > > > > > > > > id > > > > IW-02 > > > > > > 9885A004 > > > > > > 1 > > > > > > 1 > > > > > > 1 > > > > > > 2 > > > > > > 1 > > > > > > 1 > > > > > > 1 > > > > > > > > > > 3007WFP > > > > > > 1 > > > > > > 1 > > > > > > > > > > MA147LL/A > > > > > > 1 > > > > > > 1 > > > > > > 1 > > > > > > 1 > > > > > > > > > > >