[Xapian-tickets] [Xapian] #552: omindex extracts wrong extension

Xapian nobody at xapian.org
Tue Jun 28 11:52:43 BST 2011


#552: omindex extracts wrong extension
--------------------+-------------------------------------------------------
 Reporter:  Ditha   |        Owner:  olly  
     Type:  task    |       Status:  closed
 Priority:  normal  |    Milestone:        
Component:  Omega   |      Version:  1.2.4 
 Severity:  minor   |   Resolution:  fixed 
 Keywords:          |    Blockedby:        
 Platform:  All     |     Blocking:        
--------------------+-------------------------------------------------------
Changes (by olly):

  * status:  new => closed
  * version:  1.2.6 => 1.2.4
  * resolution:  => fixed


Comment:

 Thanks for your report, but this bug isn't actually present in 1.2.6 -
 {{{d.leafname()}}} returns the '''leafname''' of the file, so in the
 situation you describe, {{{d.leafname()}}} will return {{{"admen"}}} and
 the extension is empty.

 Testing (on the tip of browser:branches/1.2, but nothing relevant has
 changed there since 1.2.6):

 {{{
 #!sh
 mkdir -p 0/118/blog.laukien.com/software
 echo testing > 0/118/blog.laukien.com/software/admen
 ./omindex --follow --preserve-nonduplicates --stemmer=german -M:text/html
 --db INDEX 0
 ../../xapian-core/examples/delve INDEX -r1
 }}}

 The output from delve is:

 {{{
 Term List for record #1: D20110628 E I* M201106 Oolly P/ Ttext/html
 U/118/blog.laukien.com/software/admen Y2011 Zadm Ztesting admen testing
 }}}

 Note there's an "E" term, not "Ecom/software/admen" which there would be
 if this bug were present.

 We did used to get this wrong, but it was fixed last year in r15181, and
 the fix was released in 1.2.4.  Did you perhaps misreport the version you
 were using?

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



More information about the Xapian-tickets mailing list