similar to: Trying to patch xapian perl add/remove_spelling

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

hi, Why xapian don't support memory index/search ? I know there is a method can create memory datebase, like this: Xapian::WritableDatabase db(Xapian::InMemory::open()); *But, if i use these in multithread program, i need create many datebases!!* Xapian::WritableDatabase db1(Xapian::InMemory::open()); //used in thread1 Xapian::WritableDatabase db2(Xapian::InMemory::open()); //used in

Hi Guys, Here's a simple test case that causes a segfault with the perl bindings patched to enable spelling correction: use strict; use warnings; use Search::Xapian; my $db = Search::Xapian::WritableDatabase->new("test.db", Search::Xapian::DB_CREATE_OR_OPEN); if (!defined($db)) { die("Failed to open xapian_database: $!"); } my $indexer =

There may be some solutions?for example class XAPIAN { *static* int InitDatabase(); //for reading only, do not need lock, but if writing use lock int Search(); //safe in one object, do not need lock }; XIPIAN xp[ THREAD_NUM ]; one thread use one object, they use one database. these can be in memory with one database. 2014-06-24 20:48 GMT+08:00 Olly Betts <olly at survex.com>:

Hi All, I'm using the TermGenerator::index_text() on version 1.0.4 with the FLAG_SPELLING turned on, because the new spelling suggestion stuff seems awesome, but I'm getting a segv. (gdb) bt #0 0xb7ae153c in Xapian::WritableDatabase::add_spelling (this=0xa553988, word=@0xbff97724, freqinc=1) at ./include/xapian/ base.h:154 #1 0xb7becf47 in

I've just added a feature test for the new WritableDatabase methods - replace_document() and delete_document() with a unique term. This initially failed for inmemory due to bugs in the backend. They weren't trivial to fix and my initial attempt at a fix caused other tests to fail. I've come to the conclusion that the code there probably should be retired. It was written early on

I've uploaded Xapian 1.0.12 (including Search::Xapian 1.0.12.0), which as usual you can download from: http://xapian.org/download Here are the SHA1 checksums of the released files: fee5df9ce07c3aa16f2509a7373d48de468d9fc7 Search-Xapian-1.0.12.0.tar.gz 8a82b7e2139d2f50c95deae50b32f7bc88f63a8c xapian-bindings-1.0.12.tar.gz 963011408a77897d73da3f28e7aaabe2525e016f xapian-core-1.0.12.tar.gz

Hi to all, First, I would like to say a big thank you for the work which was done on my 'wish bug' to allow mapping one field to multiple prefixes (http://www.xapian.org/cgi-bin/bugzilla/show_bug.cgi?id=93). That's great! I have upgraded to 1.0.4 and I am revisiting my code, replacing the php query parser I wrote with Xapian's one. Everything works well, but I have some

Resurrecting an old thread from 2012! Finally got back to working on this. I have been stuck in JavaScript land for too long. Come to find out, on windows, perl does indeed define open to be win32_open and close to be win32_close. This is done in perl/lib/CORE/win3iop.h. So, to get past this problem, I had to modify Xapian.xs to do an #undef of open and close if WIN32 is defined. Also, I had

Is there a way to get a list of spelling suggestions from Xapian? Database::get_spelling_suggestion (obviously) returns just a single suggestion. Garrett

I think what i did is the same with you except i use make rather than make -sj8, and I did as root. And I do as you wrote again: root at hurricanetong-VirtualBox:/home/hurricanetong/xapian-1.2.17/xapian-core-1.2.17# ./configure [...] root at hurricanetong-VirtualBox:/home/hurricanetong/xapian-1.2.17/xapian-core-1.2.17# make -sj8 Making all in . Making all in docs Making all in tests root at

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

---------- Forwarded message ---------- From: Saad Ahmed <ch.saad.ahmed at gmail.com> Date: 3 February 2015 at 21:10 Subject: Waiting for Reply regarding "TestCases Failure" To: Xapian Development <xapian-devel at lists.xapian.org> I have been waiting for reply regarding any further steps to take. Following are the outputs of commands that you asked me to run. All these

Hi olly, I rewrote the test for PL2 after adding code to deal with negative weights. It passes on all backends other than inmemory . I see a different value of weight for inmemory backend. The code to calculate the lower bound is implemented in init().Please can I get some help with this ? -Regards -Aarsh -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

Dear Members of Xapian Project, Sorry for troubling you this time. I am currently facing a challenge that I can not search and update Xapian "InMemoryDatabase" concurrently via 2 different threads although I have added the critical area mutex which allows only reading/writing at one single time. More specifically, along with the core dump, the error message was "double free or

Hello, I've problem with xapian or sth. Ubuntu 8.04, ruby 1.9.3 with rvm, when Im trying to initialize database, Im getting this error: irb > require 'xapian' ==> true irb > database = Xapian::WritableDatabase.new('/full_path/db/xapian_db/development', Xapian::DB_CREATE_OR_OPEN) ArgumentError: Wrong arguments for overloaded method

Hi, I am a student in Pakistan willing to contribute to Xapian. I have been able to successfully build the code. But when I run the existing testcases (to verify everthing is working fine), It says 3 out of the six testcases fails. Here is the report of the test cases. "... make check-TESTS make[5]: Entering directory `/home/saad/GitProjects/xapian/build/xapian-core/tests' Running

I uninstall xapian1.3 and install xapian-1.2.17 but i still failed hurricanetong at hurricanetong-VirtualBox:~/workspace$ g++ `xapian-config --cxxflags --libs` demo2.cc /tmp/cc2wsfDJ.o: In function `main': demo2.cc:(.text+0x4a): undefined reference to `Xapian::WritableDatabase::WritableDatabase(std::basic_string<char, std::char_traits<char>, std::allocator<char> >

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 9092 > Date: 2007-06-30 15:16:16 +0100 (Sat, 30 Jun 2007) > > Log message (2 lines): > api/omdocument.cc,common/document.h,include/xapian/document.h: > Add Xapian::Document::get_docid() method. I was thinking that it would probably be useful to have a