search for: henka

Greets, WRT this discussion: http://lists.xapian.org/pipermail/xapian-discuss/2009-November/007300.html Richard recommends calling flush() before closing a index database segment, etc. Well, I can confirm that calling flush() is *required* before calling close() since close() on it's own does not commit/flush any pending writes/whatever unless the Perl script terminates, etc. So, for a

g' day Configured with --disable-maintainer-mode. Compilation of revision 13824 is failing with: common/serialise-double.cc: In function ?double unserialise_double(const char**, const char*)?: common/serialise-double.cc:141: error: ?SerialisationError? is not a member of ?Xapian? common/serialise-double.cc:157: error: ?SerialisationError? is not a member of ?Xapian?

Greetings, I've been wondering about the index format and backwards compatibility. We're using the dev version (for chert) and each svn up means that any indexes created prior to this revision cannot be read. Is this purely a cautious move to prevent errors, and, barring any obvious index format changes, can I safely force the current revision to read existing indexes? eg, by

what is the fastest way to fetch results which are sorted by timestamp ? i want to use xapian as my search engine , use add_boolean_term(something) and add_value(0,sortable_serialise(get_timestamp())) to a doc. search through enquire.set_weighting_scheme(xapian.BoolWeight()) and enquire.set_sort_by_value(0,True) to ensure that the results are sorted by the timestamp. This method is ok , but

Hi, I'm switching from UW-imap to dovecot 2.0.1 and was wondering about the mail_location config: mail_location = mbox:~/.:INBOX=/var/mail/%u Notice '.' in '~/.' above. This seems to resolve the ~/mail problem when switching from UW-imap (ie, no 'mail' prefix). doc/wiki/Migration.UW.txt doesn't mention using '~/.', so I was wondering whether there are

Greets, I'm giving a stab at patching the CPAN module to add the missing WritableDatabase::add_spelling and remove_spelling, but need a bit of guidance since I'm coming in cold, and pressed for time (aren't we all). I've modified XS/WritableDatabase.xs and added the two necessary functions, and also added the two basic tests in t/index.t. Compilation completes cleanly, but

Hi Olly, Please find attached my latest patch for the Perl spelling stuff. I've also added the missing sections in the man pages. I've left most of the unit tests out since I don't have enough experience with Xapian to comfortably code these. If you could pop those in when you get the time, that would be great. Cheers Henry Combrinck -------------- next part --------------

Greetings, Before I head off to bed I thought I'd fire off this email wrt compiling the latest svn revision. I finally resolved all the dependencies, ran bootstrap/configure, but make eventually fails with: /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../crt1.o: In function `_start': (.text+0x18): undefined reference to `main' Xapian.o: In function `boot_Search__Xapian':

Greets, Is it possible to obtain the actual match count if you're using set_collapse_key()? ie, the total count *before* the collapsing occurs (without using get_mset()). Alternatively, will MSet::get_matches_estimated() return the true - pre-collapse - count, or will it also be affected by collapsing? Thanks Henry

Greetings, I'm trying to code a test case for get_corrected_query_string() in perl in t/parser.t, but I'm getting the following error: Can't locate auto/Search/Xapian/Query/get_correct.al... I take it something isn't implemented yet? Here's the code: ok( $query = $qp->parse_query( 'one or two',

Greets, Please find attached a patch (against current svn) for consideration. It covers a few missing elements on the Perl side of things: add_spelling() and test/s. remove_spelling() and test/s. get_corrected_query_string() and test/s. get_spelling_suggestion() and test/s. man pages for the above and for WritableDatabase::close() are also patched. Please let me know of any errors (especially

Greetings, Using latest svn. I've noticed the following error when performing index merging: postlist: baseB blocksize=8K items=33962 lastblock=534 revision=1 levels=2 root=459 B-tree checked okay Tag containing meta information is corrupt. postlist table errors found: 1 I can still search on this index (I've only checked very small indexes), but merging is now a problem since I check

Greets Just tried to create a bug ticket on trac.xapian.org and it croaked with the error: ----------- Trac detected an internal error: IntegrityError: columns ticket, name are not unique The action that triggered the error was: POST: /newticket ----------- Clicking on the Create button to report the error results in an invalid URL. What's the best way to proceed to report my bug? Thanks

Greets, Just tried to add a comment to trac ticket 394. Resulted in error: Trac detected an internal error: AttributeError: 'NoneType' object has no attribute 'split' ---- My comment, for posterity, was: You may want to seriously consider pushing this patch into trunk since the performance benefit is, well, significant. My phrase test: from 15s+ down to 1s ---- regards

On Tue, March 23, 2010 19:46, Kevin Duraj wrote: > I am merging 300 indexes at once, it takes less than a day for merge > to happen for 100 million documents, during merging I notice very heavy IO. That IO sounds pretty normal. To help with IO load, we have a dedicated index store cluster, dedicated source data cluster, dedicated indexing cluster, etc. Sigh. Each time I think we have

Started a new thread - don't want to hijack the previous one (or carry on hijacking it). On Thu, June 10, 2010 05:17, Olly Betts wrote: >> My issue is that exceptions (ie, "Exception: Key too long: length >> was...") > > You are hitting the Btree key size limit. For flint and chert, this > translates to a term length limit of 245 bytes. > If you are using

Greets, I suppose this isn't a major issue, but are there any plans to complete the spelling suggestion facility across a search cluster? I seem to recall reading somewhere in the docs that it's TODO. Regards Henry

Hi, I know this is the wrong forum for this kind of question and is only ephemerally related to xapian, but maybe someone here knows and will save me some digging. Given a google PR of, say, .15 for page A of site x.com, does google "radiate" any of that PR goodness onto any other pages of site x.com? Irrespective of whether page A links to any other pages in site x.com. In other

Hi, I've been out of touch recently, so perhaps I've missed something (the last time I checked the svn pulse the Perl code was under search-xapian/ - looks like things have moved to swig). The latest trunk (revision 15699) has a problem with Perl: $tg->index_text ($text, $weight); It fails with "No matching function for overloaded 'TermGenerator_index_text'..." I

Greets, When merging lots of subindexes in batches like so: xapian-compact -m idx1 idx2... dstidx Errors such as: xapian-compact: DatabaseError: Error reading block 0: got end of file present a problem since it does not provide the offending path name (of the broken index) for easy identification/removal in automated/batch scenarios (the way DatabaseOpeningError:.... does, eg). The only way