similar to: question about trigger of reopen

On Sun, Jan 18, 2015 at 04:25:29PM +0000, James Aylett wrote: > That?s exactly how it?s supposed to work. ?Eventually? (once the > writer gets sufficiently far ahead of the reader), the reader will get > a DatabaseModifiedError and will have to re-open the database, but > until then it?s up to it when it does so. You may wish to do it every > N requests, or every K seconds, or only

Hi, I'm adapting the omega (in a Python way ;) to do search across multiple remotes database, for now, I have only one xapian-tcpsrc running, but I have documents being inserted at the same time, so (like I have readed in others e-mails) the xapian-tcpsrc throw the following message: Connection from 192.168.0.101, port 64161 Got exception DatabaseModifiedError: The revision being read has

Hello, The pod-documentation of Database.pm says: > reopen > > This re-opens the database(s) to the latest available version(s). It can be > used either to make sure the latest results are returned, or to recover from > a Xapian::DatabaseModifiedError. I really would like to do that, but as soon as this exception occures my applications dies with a SIGABRT. Is there

Hi, dear Xapianers! I've been using Xapian in my project recently. The feature "single writer, multiple reader" is one of my favorite, but currently I can't make it work. My goal is to add more documents to the database increamentally, while the Xapian search process is not stopped. I followed "quickstartindex.cc" and "quickstartsearch.cc" on

Hi all, after upgrading xapian I encountered the same problem as described in ticket #645 Read block errors after reopen() in our setup its 100% reproducible after each reopen(). I downgraded again and it seems the problem occurs in Version 1.2.16 and above. in <=1.2.15 everything works fine without seeing this error once. attaches strace shows read ends on FD. strace starts at reopen()

Hi, I am starting to see more frequent occurrences of a DatabaseModifiedError when users execute searches on my site. Since our index is being updated all the time, its easy to understand why these happen, but is it possible to ignore this error and execute the search against the stale revision? It's likely only a few seconds out of date, and if I follow the advice and reopen() the

Olly Betts <olly at survex.com> wrote: > On Wed, Aug 23, 2023 at 01:53:27PM +0000, Eric Wong wrote: > > I'm already retrying the ->get_mset operations; but now I'm > > wondering where I'd hit DatabaseModifiedErrors while inside a > > Xapian::MSetIterator loop. > > > > I assume ->get_document is a place where it gets thrown; > > but

On Wed, Aug 23, 2023 at 01:53:27PM +0000, Eric Wong wrote: > I'm already retrying the ->get_mset operations; but now I'm > wondering where I'd hit DatabaseModifiedErrors while inside a > Xapian::MSetIterator loop. > > I assume ->get_document is a place where it gets thrown; > but once a document is retrieved, can iterating through > terms in one document

On Wed, Aug 09, 2017 at 11:09:55PM +0100, Olly Betts wrote: > The Xapian exception classes aren't wrapped for Java at the moment, so > currently you'll get a java.io.IOException exception, and you can check > for DatabaseModifiedError using code like this (untested): > > try { > // Code which might cause DatabaseModifiedError. > } catch (Exception e) { Sorry,

<span style="white-space:pre"> </span>Hi£¬I am a student in China and I am using Xapian to do some projects recently, for the error DatabaseModifiedError i dont know how to catch it in java, i do not find the relative class in xapian.jar. So I write this letter for help.<div><span style="white-space:pre"> </span>So sorry to interrupt

Hi, I have read the concurrency webpage from the Xapian documentation: http://getting-started-with-xapian.readthedocs.io/en/latest/concepts/concurrency.html But it is still not clear to me how to ensure thread-safety when using libxapian (C++ API). Usually when doing multi-threading many threads can read the same variable concurrently without locking provided none of the threads modifies the

I'm already retrying the ->get_mset operations; but now I'm wondering where I'd hit DatabaseModifiedErrors while inside a Xapian::MSetIterator loop. I assume ->get_document is a place where it gets thrown; but once a document is retrieved, can iterating through terms in one document (using TermIterator) also throw DB modified? I'm dumping multiple terms per-document to a

Hi, I have previously had a problem with getting this error on a get_mset call, and solved it by subclassing XapianEnquire with a backoff-and-retry algorithm (as suggested by this list, many thanks!). However, I now get it intermittently when calling get_data on a XapianDocument. The same solution doesn't seem to be quite as easy in this case, because: 1. The document is not instantiated

Hi to all, I have Xapian 0.8.1 installed on a single processor RH9 machine with a custom 2.4.20 kernel. (I used ./configure without parameters.) I have followed the recent "threaded test" discussion here, and I have tested the examples: - Richard Boulton's example with one database, one writer, and three readers (1) works fine, I only see the expected DatabaseModifiedError. - Eric

Hello, I have updated to Xapian 1.1.4 and maybe there is a memory leak. I can run only dmalloc - valgrind would be much too slow. How can I build a debug-build of xapian? Thanks a lot Marcus

On Thu, Aug 17, 2023 at 09:28:26PM +0000, Eric Wong wrote: > In other words, is it possible to avoid duplicates if new > documents are inserted into the DB by another process in-between > ->get_mset calls when reusing Xapian::Enquire objects? The Database object itself effectively does (it works in a snapshot of the state of the database when you open it, or last called reopen() which

Hi there, My web app uses Xapian via the PHP bindings. I'm getting this error thrown occasionally when atempting to instantiate a XapianDatabase object for searching. DatabaseCorruptError: Expected block 107 to be level 1, not 0 Here's the line that invokes it: $database = new XapianDatabase(PROJROOT.'/data/xapian/posts'); And my version is xapian-core 1.2.3 with matchspy.

I'm using Search::Xapian XS from Debian stable and I'm getting what appears to be an unwrapped C++ exception: terminate called after throwing an instance of 'Xapian::DatabaseModifiedError' Using `eval' from Perl5 doesn't seem effective in catching it. I'm using postlist_begin, postlist_end and ++ to iterate a PositionIterator, and reading XS/*Iterator.xs, I see the

On Mon, Mar 27, 2023 at 11:46:04AM +0000, Eric Wong wrote: > I'm using Search::Xapian XS from Debian stable and I'm getting what > appears to be an unwrapped C++ exception: > > terminate called after throwing an instance of 'Xapian::DatabaseModifiedError' > > Using `eval' from Perl5 doesn't seem effective in catching it. > > I'm using

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.