search for: pacificair

There is is bug when setting XAPIAN_FLUSH_THRESHOLD=20000000 When trying for force Xapian flush documents to flush after 20 million documents Xapian ignores the size and flush it after only 10,000 documents. Data captured from delve after 60 seconds interval when has been set as follow: XAPIAN_FLUSH_THRESHOLD=20000000 perl -e ' while(1) { system("delve ."); sleep(60); } '

...2010-12-18 12:19 termlist.baseB -rw-r--r-- 1 kevin kevin 76G 2010-12-18 12:18 termlist.DB $ delve . number of documents = 169346678 average document length = 230970 document length lower bound = 1 document length upper bound = 3585385 highest document id ever used = 169346678 Kevin Duraj http://pacificair.com/

I've uploaded Xapian 1.0.7, which as usual you can download from: http://xapian.org/download This release fixes an assortment of bugs, and improves efficiency in a few cases. It's intended to be a relatively safe incremental update over 1.0.6. For a more detailed overview see: http://trac.xapian.org/wiki/ReleaseOverview/1.0.7 The full lists of user-visible changes are linked to from

Hello, As I know, get_matches_estimated() return an estimate for the number of documents with matches the query. But now, I found it get a disparity between the return value and real mathced number. For an example: the real matched number is 58, but the return value is 458; so when the users click the hinder page, get a blank page ... so they often complain to me. I found that the main reason is

Hi all, A few of us have been discussing whether we should have a Xapian social gathering of some kind. The current idea is meeting up in a pub in London some time in autumn for drinks and food. However all of this really depends on who might be able to come! It would be a chance to meet other Xapian enthusiasts in an informal social setting and talk about all things search-related (and

Olly and I have been discussing details of our policy for deprecating features, and we thought it would be useful to canvas users opinions on a particular aspect. From time to time, we remove features from the library (usually because we have a better replacement). To make life easier for users, we've been following a deprecation policy, so that users are given plenty of warning of