similar to: Re: [Xapian-commits] 8351: trunk/xapian-core/ trunk/xapian-core/backends/flint/

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

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

hi, I'm using Xapian on Windows with large files. My index directory is about 65 607 466 693 bytes: 2007-01-30 09:28 17 position_baseA 2007-01-30 10:06 17 position_baseB 2007-01-23 14:18 0 position_DB 2007-01-30 10:06 360 496 postlist_baseB 2007-01-30 10:06 23 623 852 032 postlist_DB 2007-01-30 10:06 88 432

On Mon, Apr 09, 2007 at 11:26:44AM +0100, richard wrote: > backends/flint/flint_database.cc: Fix bug with document lengths > in replace document. Was using doclens.insert() to set the new > document length, but this has no effect if the entry already > exists. Argh! That issue has bitten us at least once before. I'll audit all uses of insert to see if there are any other

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

Hi, I am new to xapian and read somewhere that xapain was using flint before released version 1.1 now it is using chert. I am looking for differences between both flint vs chert respective to xapian and advantages of chert. thanks Smriti

Hi, What's the main difference between chert and flint? What above vs lucene? I am mainly asking about data structure (lexicon, posting list, document data), what's in memory, what's on disk, hash vs b-tree and reasons behind them. Any pointer is appreciated. Thanks! Crystal -------------- next part -------------- An HTML attachment was scrubbed... URL:

I've just noticed that new indexes no longer have position.{DB,baseA,baseB} files, all previous indexes (I roll indexes every week using xapian-compact) have the position files. The index seems to work but it is returning some odd results, for example if I run a query with the phrase "machine learning" it mostly returns documents containing "machine learning" but it also

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

Hello, I'm using Xapian 1.0.2 (flint) and matching Search::Xapian. I'm getting: terminate called after throwing an instance of 'Xapian::DocNotFoundError', which dumps core. at first it was after adding my 2nd document (to an empty db, although I don't know if that has any bearing) to the database with a replace_document() call. I shifted the first document off the

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

Report by Eric Lindblad 13-09-2015 http://www.ericlindblad.blogspot.com cf: http://comments.gmane.org/gmane.comp.search.xapian.general/9862 I ported xapian-core-1.2.21 to Interix today having disabled the default chert and development brass backends, using flint, which was the 1.0.x series' default, which ships with the 1.2.x series; the disabling do to an unresolved 'ambiguous

Folks, OK found it, omega.cc looks for multiple DB definitions and adds it to the search list. If the dbs are only one directory lower (e.g. not in default as in beta/default, but only "beta"), then modifying database_dir setting as follows will work: database_dir /svr/hda1/xapian then, ./omega.cgi 'P=pda' FMT='xml' DB="beta" DB="gamma"

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

Hi, Apologies for the many replies. I have found this documentation: http://www.lehman.cuny.edu/cgi-bin/man-cgi?ugen+7 (I am using the ugen driver). Richard On Sun, Apr 5, 2015 at 3:34 AM Richard Flint <richard.flint at gmail.com> wrote: > Hi, > > I have to admit this sounds like it could screw up the system if not done > right - particularly because the solaris packaging

Hi, I couldn't get openusb to make successfully but the good news is that Solaris seems to include openusb in the package repository and I have now installed it: ./usr/lib/libopenusb.so.0.0.1 Any idea how i can get NUT to build against this libopenusb which has been installed by Solaris? Regards, Richard On Sun, Apr 5, 2015 at 4:20 AM Charles Lepple <clepple at gmail.com> wrote:

I've uploaded Xapian 1.0.19 (including Search::Xapian 1.0.19.0), which as usual you can download from: http://xapian.org/download The most notable changes in this release are: QueryParser: * Fix memory leak if Database throws an exception during parsing. Flint backend: * Updating positional information for a document optimised a little. Search::Xapian: * Wrap

I've uploaded Xapian 1.0.18 (including Search::Xapian 1.0.18.0), which as usual you can download from: http://xapian.org/download The most notable changes in this release are: QueryParser: * Improve support for languages such as Burmese which use Unicode enclosing mark and combining spacing mark characters. Flint backend: * When updating documents, don't update posting entries

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

Hi, I've a program which: 1. Sets XAPIAN_FLUSH_THRESHOLD=1000 2. Opens a (new) database for write 3. Indexes a few thousand documents 4. Periodically also does queries on the database With 1.1.4, with certain document sets (basically a particular mail folder of mine), Enquire.get_mset() sometimes (but not always) triggers a "RangeError: Value in posting list too