[Xapian-tickets] [Xapian] #340: PostingSource subclasses cannot signal a change in their maxweight

[Xapian]

#340: PostingSource subclasses cannot signal a change in their maxweight
-------------------------+--------------------------------------------------
 Reporter:  richard      |        Owner:  olly     
     Type:  defect       |       Status:  new      
 Priority:  normal       |    Milestone:  1.1.1    
Component:  Library API  |      Version:  SVN trunk
 Severity:  normal       |   Resolution:           
 Keywords:               |    Blockedby:           
 Platform:  All          |     Blocking:           
-------------------------+--------------------------------------------------

Comment(by olly):

 OK, this looks good so I've committed the !PostingSource end of things to
 trunk as r12694.  Please take a look and tell me if this looks sane or
 not.

 Currently this is crudely bolted to the matcher to just force a recursive
 call to {{{PostList::recalc_maxweight()}}} - I'm going to work on that
 part next.

 Possibly ''"tell the matcher the change in maxweight"'' should be the
 '''only''' mechanism, and also used by all the other postlists - it would
 certainly be nicer if a reduction in maxweight didn't require work
 proportional to the size of the query.  I will look at how feasible that
 is.

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