similar to: Database Locking

On Sun, 21 Feb 2016 22:33:22 +0000, Olly Betts <olly at survex.com> wrote: > On Sun, Feb 21, 2016 at 02:15:25PM +0100, Eric J wrote: > > I discovered, while trying to set up Tcl bindings for Notmuch > > (https://notmuchmail.org/), which uses Xapian, that flintlock was not > > being locked (I had lost updates). > > It seems to work for me, testing with this: >

Xapian (0.7.5) is spitting out this error on a regular basis: org.xapian.errors.DatabaseError: Error reading block 136618: got end of=20= file =A0=A0=A0=A0=A0=A0=A0 at=20 org.xapian.XapianJNI.writabledatabase_repalce_document(Native Method) =A0=A0=A0=A0=A0=A0=A0 at=20 org.xapian.WritableDatabase.replaceDocument(WritableDatabase.java:67) I don't have a gdb backtrace, only the Java

I discovered, while trying to set up Tcl bindings for Notmuch (https://notmuchmail.org/), which uses Xapian, that flintlock was not being locked (I had lost updates). I then found that opening a Xapian database for writing directly via the Xapian Tcl bindings also silently fails to lock flintlock. I have taken a copy of flint_lock.cc to play with, and I find that it locks the file when called

On Wed, 24 Feb 2016 03:17:35 +0000, Olly Betts <olly at survex.com> wrote: >On Mon, Feb 22, 2016 at 12:26:27PM +0100, Eric wrote: >> On Sun, 21 Feb 2016 22:33:22 +0000, Olly Betts <olly at survex.com> wrote: >>> On Sun, Feb 21, 2016 at 02:15:25PM +0100, Eric J wrote: >>>> I discovered, while trying to set up Tcl bindings for Notmuch >>>>

Hi all, I've been toying with xapian (mostly using the Python bindings) and I think I've hit a bug in the TermIterator::skip_to() method (or maybe in QuartzAllTermsList::skip_to()). I've attached a c++ source file that demonstrates the issue. In short, if you have a WritableDatabase, ask for the all-terms TermIterator with db.allterms_begin(), and then skip_to() a word that is itself

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> >

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

I seem to be seeing cases where I call db.delete_document(somedocid) with no error, then flush() and delete the database object, but the document is still there after process exit. The write lock is normally deleted, so it appears that the database close finished normally. If I then then call delete_document(somedocid) from another command/process, this time it goes away. I've been seeing

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

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

Hi, I am using the Xapian-0.8.0 snapshot from 15-Apr-2004 02:14, and I am using the same Xapian::WritableDatabase instance for indexing and searching. Currently each search causes a database flush, which is slow. How can I avoid this flush? It seems that I have to modify Xapian to either - search only the already flushed data (eventually missing some hits) or - search the un-flushed data, too.

The disclaimer automatically added and is not intended to limit legitimate discourse, and any code I write for this is expected to be licensed under whatever license the original work is using. I haven't tried compiling latest code under visual studio yet (is this possible?). I wonder if there is a way to tell gcc to not mangle the names during cross compile. I was able to successfully

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

I recently lost a hard drive and after successfully restoring everything, I think, I'm getting "Error opening database `current.1': DatabaseOpeningError: Couldn't detect type of database" The directory current.1 contains the following files: -rw-rw-r-- 1 jwl jwl  30064640 Aug 28 23:44 docdata.glass -rw-rw-r-- 1 jwl jwl       151 Aug 28 23:44 iamglass -rw-rw-r-- 1 jwl jwl

Hello list, looks like one can open a Xapian database in read-only mode and do the following: $db = Search::Xapian::Database->new("/foo/bar/"); $enq = $db->enquire("XIDblub"); the same doesn't seem to be possible with a database opened in read-write mode: $db = Search::Xapian::WritableDatabase->new("/foo/bar/",

Hi, Trying to learn Search::Xapian and be better at perl at the same time, I'm stuck, at the DB_CREATE_OR_OPEN error. Perl says this: ~/dev/sandbox/Xapian-perl$ ./Index1-Xap.pl 100-objects-v1.csv db "db" is not exported by the Search::Xapian module Can't continue after import errors at ./Index1-Xap.pl line 7. BEGIN failed--compilation aborted at ./Index1-Xap.pl line 7. What I

Hi, As part of my whole indexing thing, I want to move the databases around, from within the code. So, I figured that the safest bet would be to close the DB before attempting to move it. But there's no Xapian::Database::close() or even Xapian::WritableDatabase::close(). I have a global variable that holds the database, and I open it in the main(): // globals Xapian::WritableDatabase

Hi, I've compiled xapian 1.0.9 (core and buildings) on Windows Xp, using Lemur's nmake files[1]. I'm trying to use acts_as_xapian [2] on RubyOnRails, but I'm facing a problem with the rebuild index process. in acts_as_xapian, to rebuild the index, a new Xapian::WritableDatabase is created with a different path, then flush() is invoked; lastly, the new path is renamed to the old

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

Greetings, We use NFSv4 on our cluster and perform distributed indexing (well, we used to on our previous system which used a simple touch() locking mechanism). I'm having a spot of bother getting Xapian to obtain a lock (hangs on fcntl64()). I've read http://trac.xapian.org/wiki/XapianOverNFS and other list posts, and noted that a lock daemon should be running to allow locks