[Xapian-tickets] [Xapian] #433: MatchSpy should allow early termination

[Xapian]

#433: MatchSpy should allow early termination
-------------------------+--------------------------------------------------
 Reporter:  richard      |       Owner:  olly     
     Type:  enhancement  |      Status:  new      
 Priority:  normal       |   Milestone:  1.1.7    
Component:  Matcher      |     Version:  SVN trunk
 Severity:  normal       |    Keywords:           
Blockedby:               |    Platform:  All      
 Blocking:               |  
-------------------------+--------------------------------------------------

Comment(by olly):

 (Ignoring the smiley) it's not a vote for any implementation approach.
 It's a vote for focussing on getting 1.2.0 released, and in particular not
 being distracted by new features or enhancing existing features when we
 should be addressing bug reports from users testing 1.1.x and trunk, plus
 the few existing tickets we've previously agreed should be addressed.

 We were talking (albeit rather  speculatively) about July 2009 for 1.2.0
 at one point, so we're now more than 6 months late.

 This particular ticket is at worst an efficiency issue (since the
 !MatchSpy can as you say just do nothing when called).  It would be nice
 to address for 1.2.0 to avoid a possible API change in the future, but
 we've already punted on tickets which would be at least as useful to
 address.  It isn't obvious what the best approach here is.  If we rush to
 fix it, we increase the risk of being stuck with an API which may later
 prove problematic.  We also risk introducing bugs and further delaying
 1.2.0.

 Marking !MatchSpy as experimental is a possible option, but we don't
 really want to be making ABI-changes mid-1.2.x as we'll have to carry the
 weight of both old and new implementations until 1.3.0.

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