[Xapian-tickets] [Xapian] #178: No remote backend support for: spelling correction, synonyms, matchdecider

[Xapian]

#178: No remote backend support for: spelling correction, synonyms, matchdecider
----------------------------+-----------------------------------------------
 Reporter:  richard         |        Owner:  nobody   
     Type:  defect          |       Status:  new      
 Priority:  normal          |    Milestone:  1.1.5    
Component:  Backend-Remote  |      Version:  SVN trunk
 Severity:  normal          |   Resolution:           
 Keywords:                  |    Blockedby:           
 Platform:  All             |     Blocking:           
----------------------------+-----------------------------------------------
Changes (by richard):

  * owner:  richard => nobody
  * status:  assigned => new


Comment:

 It might be a good idea to deprecate !MatchDecider for 1.2.0 (for removal
 in 1.3.0?), but I think we should try and provide an easy migration path
 for users (which would be a !PostingSource which implemented the
 !MatchDecider interface, so users could simply subclass that posting
 source and filter the query with it).  !PostingSource classes are quite a
 bit more fiddly to implement than !MatchDecider classes.

 I'm not 100% sure we should deprecate the !MatchDecider interface - while
 it can be replicated with a !PostingSource, it's a more convenient API.
 We could change the internal implementation to use a PostingSource, which
 would allow us to simplify the matcher code.  For this reason, I don't
 think there's much need to hurry to deprecate !MatchDecider.

 I've emailed Paul Rudin to ask if he wants to submit the spelling patch to
 this ticket.

 I don't have time to work on this ticket in the near future, so assigning
 it to "nobody" for clarity.

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