RE: Which fields matched?

2012-12-11 Thread Jeff Wartes
, December 08, 2012 7:36 PM To: solr-user@lucene.apache.org Subject: Re: Which fields matched? We've used lucene-1999 with some success in ActiveMath to find the language that was matched. paul Le 8 déc. 2012 à 10:09, Mikhail Khludnev a écrit : Jeff, explain() algorithm is definitely too slow

Re: Which fields matched?

2012-12-08 Thread Mikhail Khludnev
: Which fields matched? The debugQuery explain is simply a text display of what Lucene has already calculated. As such, you could do a custom search component that gets the non-text Lucene Explanation object for the query and then traverse it to get your matched field list without all the text

Re: Which fields matched?

2012-12-08 Thread Paul Libbrecht
. -Original Message- From: Jack Krupansky [mailto:j...@basetechnology.com] Sent: Friday, December 07, 2012 10:47 AM To: solr-user@lucene.apache.org Subject: Re: Which fields matched? The debugQuery explain is simply a text display of what Lucene has already calculated

Which fields matched?

2012-12-07 Thread Jeff Wartes
If I have an arbitrarily complex query that uses ORs, something like: q=(simple_fieldtype:foo OR complex_fieldtype:foo) AND (another_simple_fieldtype:bar OR another_complex_fieldtype:bar) I want to know which fields actually contributed to the match for each document returned. Something like:

Re: Which fields matched?

2012-12-07 Thread Jack Krupansky
be required, but the Explanation structure could get messy. -- Jack Krupansky -Original Message- From: Jeff Wartes Sent: Friday, December 07, 2012 11:59 AM To: solr-user@lucene.apache.org Subject: Which fields matched? If I have an arbitrarily complex query that uses ORs, something like: q

RE: Which fields matched?

2012-12-07 Thread Jeff Wartes
[mailto:j...@basetechnology.com] Sent: Friday, December 07, 2012 10:47 AM To: solr-user@lucene.apache.org Subject: Re: Which fields matched? The debugQuery explain is simply a text display of what Lucene has already calculated. As such, you could do a custom search component that gets the non

Re: Knowing which fields matched a search

2012-03-12 Thread Russell Black
Paul, I would think debugQuery would make it slower too, wouldn't it? Where is the thread you are referring to? Is there a lucene jira ticket for this? On Mar 11, 2012, at 9:38 AM, Paul Libbrecht wrote: Russel, there's been a thread on that in the lucene world... it's not really perfect

Re: Knowing which fields matched a search

2012-03-11 Thread Paul Libbrecht
Russel, there's been a thread on that in the lucene world... it's not really perfect yet. The suggestion to debugQuery gives only, to my experience, the explain monster which is good for developers (only). paul Le 11 mars 2012 à 08:40, William Bell a écrit : debugQuery tells you. On

Re: Knowing which fields matched a search

2012-03-10 Thread William Bell
debugQuery tells you. On Fri, Mar 9, 2012 at 1:05 PM, Russell Black rbl...@fold3.com wrote: When searching across multiple fields, is there a way to identify which field(s) resulted in a match without using highlighting or stored fields? -- Bill Bell billnb...@gmail.com cell 720-256-8076

Knowing which fields matched a search

2012-03-09 Thread Russell Black
When searching across multiple fields, is there a way to identify which field(s) resulted in a match without using highlighting or stored fields?