Re Mike's delegating custom query suggestion - see https://issues.apache.org/jira/browse/LUCENE-1999
----- Original Message ---- From: Michael McCandless <[email protected]> To: [email protected] Sent: Mon, 15 February, 2010 10:03:30 Subject: Re: Further refinement of search results - distinguishing hits with exact phrase match from the rest I don't think Lucene makes this easy, today, out of the box. The scoring process for a boolean query doesn't track which sub-clause had matched. Though, it does track the number of clauses that matched (coord). EG you'd be able to tell that a given hit had both clauses match, vs only 1 (just not which one). But coord is not current exposed - you'd have to modify BooleanScorer/2 to make that available per hit. Alternatively, you could make a simple custom query that delegates all scoring to another query, but tracks whether it matched a given document. Then, you'd make your own custom Collector that, on seeing a competitive hit, also records which clause of the query had matched. Mike On Mon, Feb 15, 2010 at 12:19 AM, micmit <[email protected]> wrote: > > I run a query, say, NAME:"John Smith"^1.5 OR NAME:(Jo* Smith). > > Once I get the result set, is there an efficient way to identify those hits > that match: a) "John Smith" b) Jo* Smith ---? > > or perhaps to change the original query somehow ? > -- > View this message in context: > http://old.nabble.com/Further-refinement-of-search-results---distinguishing-hits-with-exact-phrase-match-from-the-rest-tp27589728p27589728.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
