[Xapian-tickets] [Xapian] #375: Merge postingsources branch

[Xapian]

#375: Merge postingsources branch
-------------------------+--------------------------------------------------
 Reporter:  olly         |       Owner:  richard 
     Type:  enhancement  |      Status:  assigned
 Priority:  high         |   Milestone:  1.1.3   
Component:  Library API  |     Version:          
 Severity:  normal       |    Keywords:          
Blockedby:               |    Platform:  All     
 Blocking:               |  
-------------------------+--------------------------------------------------

Comment(by olly):

 Access to values in flint was very slow too, and values are generally
 larger than the encoded doclength (or wdf of a term), so fewer fit in a
 chunk.  If you want to check timings, try using chert with BM25 parameters
 such that the document length isn't used.

 I think if chert really isn't ready to replace flint, it would be better
 to backport valuestats to flint (which has wider benefits, such as
 allowing the new omindex "don't reindex unchanged documents" feature to
 work efficiently), or to consider backing out the document length change
 from chert (though I think it's probably likely to be a general win for
 most users - your test only considered the case where there's plenty of
 RAM, and only used single term queries rather than a realistic mix).

 So I don't think we should add !LimitedValueWeightPostingSource currently.
 We can of course review that nearer the release.

 Looking at the diff to the last merge point, for consistency, name()
 '''shouldn't''' include "()" at the end of the returned name, but
 '''should''' include a "Xapian::" prefix.

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