[Xapian-tickets] [Xapian] #183: Remote backend should support use of Xapian::MatchDecider

[Xapian]

#183: Remote backend should support use of Xapian::MatchDecider
----------------------------+-----------------------------------------------
 Reporter:  richard         |        Owner:  richard  
     Type:  defect          |       Status:  assigned 
 Priority:  normal          |    Milestone:  1.1.2    
Component:  Backend-Remote  |      Version:  SVN trunk
 Severity:  normal          |   Resolution:           
 Keywords:                  |    Blockedby:           
 Platform:  All             |     Blocking:           
----------------------------+-----------------------------------------------

Comment(by richard):

 I've been working on a patch to do this.  The hardest part so far has been
 adding a MatchSpy parameter to get_mset().  Since we're planning to
 deprecate MatchDecider, I would like to add a new get_mset() overload with
 the signature:

 {{{
     MSet get_mset(Xapian::doccount first,
                   Xapian::doccount maxitems,
                   Xapian::doccount checkatleast,
                   const RSet * omrset,
                   MatchSpy * matchspy) const;
 }}}

 However, I can't make this work without creating ambiguities with the
 existing get_mset() methods.  My favoured solution for now is to add this
 method with a different name (ie, get_mset_with_matchspy), but this seems
 less than ideal.

 Other than this difficulty, I'm making good progress - I'll probably apply
 the patch to the matchspy branch, and modify the matchdecider subclasses
 there to be matchspy subclasses, since this will offer an easy way to test
 with the remote backend.

-- 
Ticket URL: <http://trac.xapian.org/ticket/183#comment:7>
Xapian <http://xapian.org/>
Xapian