You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucy.apache.org by "Marvin Humphrey (JIRA)" <ji...@apache.org> on 2010/06/18 03:20:22 UTC
[jira] Resolved: (LUCY-111) Matcher
[ https://issues.apache.org/jira/browse/LUCY-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marvin Humphrey resolved LUCY-111.
----------------------------------
Resolution: Fixed
Committed as r955810.
> Matcher
> -------
>
> Key: LUCY-111
> URL: https://issues.apache.org/jira/browse/LUCY-111
> Project: Lucy
> Issue Type: New Feature
> Components: Core - Search
> Reporter: Marvin Humphrey
> Assignee: Marvin Humphrey
> Priority: Blocker
> Attachments: Matcher.bp, Matcher.c, Matcher.pm
>
>
> A Matcher is an object which matches a set of Lucy doc ids, iterating over
> them via Next() and Advance(). It combines the roles of Lucene's
> DocIdSetIterator and Scorer classes.
> Some -- but not all -- Matchers implement a Score() method. We can refer to
> such Matchers informally as "scorers", but Lucy won't need a Scorer class a la
> Lucene. In Lucy, Query classes will compile down to Matchers that either
> Score() or don't. This allows us to perform optimizations on branches of
> compound scorers: compiling "foo AND NOT bar" will produce a scoring Matcher
> for "foo" and a non-scoring Matcher for "bar", since the "bar" branch can
> never contribute to the score.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.