similar to: Asking Help

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,

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 all, Currently I'm implementing a retrieval system with multiple reader processes and only one writer process updating the database periodically. In a reader process, whenever a Xapian::DatabaseModifiedError exception is caught, I call function reopen() and retry. However, my problem is, when there is only a small set of modification, e.g. only one new document is added, the reader would

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

Im doing an aplication in Java and i have a program made in R what i want to launch with Java. I have the following instructions: Runtime r = Runtime.getRuntime(); try { System.out.println ("Llamada a R..."); p = r.exec(sRutaR); } catch (IOException e) { System.out.println ("Error lanzando R: " +

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

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

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

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

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

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

I'm one of the developers of Notmuch, an email client that makes extensive use of Xapian. For some time, full multi-version concurrency control (MVCC) has been on our wish list. Olly mentioned that brass now uses free lists---a key step toward full MVCC---and I offered to pitch in on putting the other pieces into place. Before I wade too deep into this, I wanted to propose my plan. Full

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

Hi, I have a user reporting the following error during recoll indexing: flush() failed: Db block overwritten - are there multiple writers? "flush() failed" is from recoll, the rest is, I think the text of the Xapian exception. This is with Xapian 1.4.3 on Linux (I asked for more details, should be coming). I don't think that I've ever seen this error, and I also

On Sat, Apr 08, 2017 at 09:11:22PM +0100, James Aylett wrote: > On 8 Apr 2017, at 19:15, Vivek Pal <vivekpal.dtu at gmail.com> wrote: > > >> and the details of which weighting schemes were available in which version > >> isn't a key part of the $set command itself. > > > > Do you suggest dropping that piece of information out? Since the reason behind

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

Should tablegen detect this as an error, or is it documented as a limitation somewhere that we've missed? In the tablegen-generated file AMDILGenIntrinsics.inc, we have a bunch of if statements comparing strings, many of which are dead, preventing correct recognition of some intrinsics in the their text form. I'm not quite sure what GET_FUNCTION_RECOGNIZER is used for, but if it's

If the source being scanned has "llvm.AMDIL.barrier.global, it will match the first barrier test and return AMDIL_barrier, not AMDIL_barrier_global. On Nov 29, 2012, at 7:19 PM, Chris Lattner <clattner at apple.com> wrote: > Out of curiosity, what is wrong about that? It looks ok to me. > > -Chris > > On Nov 29, 2012, at 6:52 PM, "Relph, Richard"