[Xapian-tickets] [Xapian] #250: replace_document should make minimal changes to database file

Xapian nobody at xapian.org
Wed Jan 27 08:55:53 GMT 2010


#250: replace_document should make minimal changes to database file
---------------------------+------------------------------------------------
 Reporter:  richard        |        Owner:  richard  
     Type:  enhancement    |       Status:  closed   
 Priority:  normal         |    Milestone:  1.0.18   
Component:  Backend-Chert  |      Version:  SVN trunk
 Severity:  normal         |   Resolution:  fixed    
 Keywords:                 |    Blockedby:           
 Platform:  All            |     Blocking:           
---------------------------+------------------------------------------------
Changes (by olly):

  * status:  assigned => closed
  * resolution:  => fixed
  * milestone:  1.2.x => 1.0.18


Comment:

 Backported all the relevant changesets to 1.0 in r13849.  Testing in real
 world applications is most welcome.

 I think we should look at whether it's better to encode the new positions
 and compare the encoded form with the old encoded form (rather than decode
 the old form, iterate it and the new form to compare, and if they differ
 encode the new form) as I suspect that's going to be faster for the
 "unchanged" case, and it clearly is going to be for the "changed" case.
 I've filed #428 for this.

 I also wonder if the Document object should track the changes made, rather
 than copy the old data and modify it.  Currently adding a new term to a
 document is unnecessarily O(number of terms indexing that document).  The
 current optimisation is still useful in the case of reindexing an
 unmodified (or slightly modified) document from the original source.  I've
 filed #429 for this.

 So closing this ticket now.

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



More information about the Xapian-tickets mailing list