similar to: Need Help

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

Flint failed to deliver indexing performance to Quartz. I am proposing to remove Flint as default database and place Quartz database back as default. The catch is not that Flint database is smaller and faster during searches then Quartz database as developers were concerning when were measuring and neglecting to measure performance when creating the large indexes. The truth is that Flint

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

Thanks Olly, I have given flint a go -and it is generally much quicker (once it has loaded the cache -that process still takes minutes). Flint actually seems tro do some caching whereas quartz just seemed to hit the disc constantly. Generally I've been running it on a machine with 5G of memory -but it has to contend with other processes for resources, I have also run it on its own on a 1G

On Tue, Jan 02, 2007 at 03:55:59PM +0000, richard wrote: > * backends/quartz/btree.cc,backends/flint/flint_io.h: Patches from > Charlie Hull to allow 2GB+ index files work when compiled using > Visual C++. I suspect that xapian-compact.cc (and quartzcompact.cc if you can be bothered) will also need fixing since they use off_t. You need to make sure that the stat() function called

olly wrote: > Log message (6 lines): > backends/flint/flint_database.cc: Delete the corresponding entry > (if any) from doclens in delete_document(). Add assertion to > add_document_() that the corresponding entry in doclens isn't > already set, but in a non-debug build overwrite any existing > entry as that's more likely to be correct. >

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

Locking of Quartz databases is currently done with a lockfile. This works well from the actual locking side, but the downside is that the lock isn't released if a process doesn't destroy the Xapian::WritableDatabase object. This is made worse because some of the bindings don't call destructors (or don't do it reliably). The obvious alternative is to use actual locking APIs. On

I've some trouble with my indexer, which builds on simpleindex.cc. The problem is that indexing process becomes very slow after we indexed 2000k docs (though the indexer works quite well with first 2000k docs). It took almost three weeks to index 8 million docs. However, we need to index about 20 million docs. I have to stop the indexer due to its performance. I think my question is

Hello Arjen van der Meijden, on xapian-discuss you mentioned that your Xapian installation has got up to 15 GB database size. Can you tell me about the largest index filesize you got? According to <http://xapian.org/docs/scalability.html>, it seems that the quartz database filesize is limited only by the OS and file system. Can you confirm from your experience that there is no 2GB limit?

Hi, I configured XAPIAN 1.0.1 and OMEGA 1.0.1. on my development machine (first removed the old ones). I recreated my databases (both quartz and flint) and tried to run original queries against the databases created by the new versions. I'm getting empty result sets from OMEGA. If I use the delve tool I actually see that the records are created fine. No log files are written as far as I

Just got this error when replacing (updating) a document in the xapian index (using php bindings): Fatal error: Uncaught exception 'Exception' with message 'DatabaseError: Error reading block 16908825: got end of file' Does anyone know what this means exactly? Alec

On Thu, Mar 01, 2007 at 03:29:26PM +0000, richard wrote: > * common/utils.c,common/utils.h: For windows, add an om_tostring()function for > 64 bit integers: time() and GetProcessId() return these, and without this, > backends/quartz/quartz_log.cc reports an error. This change generates a new warning in the mingw cross-build: common/utils.cc:82: warning: int format, different type

We have: ---------------------------------------------------------------------- typedef unsigned long uint4; ---------------------------------------------------------------------- which on an LP64 system is a lie. If uint4 is used on disk (and it's used in the btree implementation) then it would make the databases unportable, which probably isn't a good idea (unless we already have

Hi all, Attached is a simple patch for Flint and Quartz; Visual C++ complains if you try and define arrays with non-constant size. Charlie -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch7.patch URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20070423/d92c683a/attachment.ksh>

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

Quartz has a QuartzDiskTable class which is a thin wrapper for a pair of Btree objects (or just one if the table is opened readonly): http://www.xapian.org/docs/sourcedoc/html/classQuartzDiskTable.html There's also a QuartzBufferedTable class which adds memory buffering of changes to this: http://www.xapian.org/docs/sourcedoc/html/classQuartzBufferedTable.html However, as of 0.8.0 we now

Hello, Would anyone object to my submitting an entry for xapian-core to the FreeBSD ports collection ? This would make it even easier for any FreeBSD user to install a xapian-based application. By the way, it does not seem quite right that xapian-core 0.9 will install commands with such generic names as 'copydatabase' or 'simplesearch' to /usr/local/bin by default. Either a

A short note: this message comes as a public reply to a discussion about xapian-bindings, that is why it can look a little bit incomplete... however the problem for now was to modify the xapian-core distribution so that there are symbols #defined (or maybe #undefined) to reflect what backends were available in the library. As I said to Olly, I'm a complete newbie at Autotools (and SWIG), so

PHRASE QUERY Xapian::Query((MBOX:12345678-1234-1234-1234-1234567890ab AND (LP:backup:(pos=1) PHRASE 6 LP:c::(pos=2) PHRASE 6 LP:program files:(pos=3) PHRASE 6 LP:Mozilla Firefox:(pos=4) PHRASE 6 LP:res:(pos=5) PHRASE 6 LP: table-add-column-after-hover.gif:(pos=6)))) AND QUERY Xapian::Query((MBOX:12345678-1234-1234-1234-1234567890ab AND LP:backup:(pos=1) AND LP:c::(pos=2) AND LP:program