, 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
: 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
.
-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
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. No parsed would be
[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
