search for: copydatabase

...d 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 renaming or a configure option to control the installation for the examples directory would be really nice. Would you accept a patch to allow configure to disable the building and installation of the examples directory (ie: --di...

...don't provide an implementation of wdf_upper_bound(), the default is to use the collection frequency of the term, so provided that information is available in the lucene files, the lack of wdf_upper_bound information isn't a show stopper. > I think this data will be caculated when doing copydatabase, I will update > the code later That's probably a good plan though. Cheers, Olly

I am getting this error when trying to remove a document from my Xapian database via writabledatabase_delete_document: "DatabaseCorruptError: Db block overwritten - are there multiple writers?" There might have been two processes trying to write to it earlier today, but currently only one process can touch it at a time, and I still receive the error. Is there a fast way to fix this

...name:term1 AND field_name:term2 Until now, I found some data needed for BM25 in Xapian are not existed in Lucene: 1. doclength_lower_bound?doclength_upper_bound 2. wdf_lower_bound?wdf_uppper_bound 3. total_length 4. doclength(for each document) 1-3 are statistics data, can be caculated when doing copydatabase, and store them in somewhere. But doclengh is hard to do this way. 1. some other data instead of doclength? 2. Xapian support other rank algorithm which does not need doclength? Is there some suggestions to solve this problem? And the demo patch is here: https://github.com/white127/xapian-patch/b...

I posted this message first. But it was missing so I post again. I think there is a some bug in build configration files. Can you check up the following errors and fix it? The error has no concern with UTF-8 patch. Environment : CentOS 4.3 x86_64 Sungsoo Kim ---------------------------------- [root at saturn xapian-core-0.9.4_svn6707]# make ... ... mkdir .libs/libxapian.lax/libqueryparser.a

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 Mon, Aug 26, 2013 at 09:41:07AM +0800, jiangwen jiang wrote: > > For now, using weighting schemes which don't use document length is > > probably the simplest answer. > > There's tf-idf weighting scheme on svn master, is it suitable for lucene > backend? Yes - TfIdfWeight doesn't ever use the document length (at least with the normalisations currently

...?/usr/bin/mkdir -p '/root/rpmbuild/BUILDROOT/xapian-core-1.4.15-1.x86_64/usr/bin' ? /bin/sh ./libtool?? --mode=install /usr/bin/install -c bin/xapian-delve bin/xapian-check bin/xapian-compact bin/xapian-progsrv bin/xapian-replicate bin/xapian-replicate-server bin/xapian-tcpsrv examples/copydatabase examples/quest examples/simpleexpand examples/simpleindex examples/simplesearch examples/xapian-metadata examples/xapian-pos '/root/rpmbuild/BUILDROOT/xapian-core-1.4.15-1.x86_64/usr/bin' libtool: warning: 'libxapian.la' has not been installed in '/usr/lib64' libtool: ins...

Greetings, I've been wondering about the index format and backwards compatibility. We're using the dev version (for chert) and each svn up means that any indexes created prior to this revision cannot be read. Is this purely a cautious move to prevent errors, and, barring any obvious index format changes, can I safely force the current revision to read existing indexes? eg, by

The issue is that delve was renamed to xapian-delve but documentation is still saying that delve is delve. Who has access to update the documentation? http://www.linuxfromscratch.org/blfs/view/svn/general/xapian.html Installed Programs: copydatabase, delve, quest, simpleexpand, simpleindex, simplesearch, xapian-check, xapian-chert-update, xapian-compact, xapian-config, xapian-inspect, xapian-metadata, xapian-progsrv, xapian-replicate, xapian-replicate-server and xapian-tcpsrv On Wed, Jul 6, 2016 at 1:15 PM, Kevin Duraj <kevin.duraj at zefr...

...out this will be fairly easy to > > resolve. > > > > On Mon, Jun 12, 2006 at 11:35:53AM -0800, oscaruser@programmer.net wrote: > > > I think it may also be time to develop a tool to validate the integrity > > > of a flint index. > > > > If you can run copydatabase on a database, it's in good shape with the > > possible exception of the postlist table. > > > > If you want something more specific, quartzcheck is probably a good > > starting point. The flint and quartz formats still have quite a bit > > in common. > > &g...

I have installed the new Xapian 1.4.0 , during the installation, I haven't seen any problems, however, when I execute commands quest and delve I get different versions, and my Perl-based searches return Exception: Couldn't detect type of database ... and what are these glass things in the index directories? There is a no new version of Perl Search::Xapian. $ quest -version quest -

We've had some catastrophic filesystem failures that have left us with corrupted databases with empty files and no backup for about 15TB of our data. Recreating the 15TB from source data backups is possible but will take a very very long time. I'm hoping that, given all of the .DB files are still intact, there my be some way to extract their contents and rebuild the other tables. This

what is the fastest way to fetch results which are sorted by timestamp ? i want to use xapian as my search engine , use add_boolean_term(something) and add_value(0,sortable_serialise(get_timestamp())) to a doc. search through enquire.set_weighting_scheme(xapian.BoolWeight()) and enquire.set_sort_by_value(0,True) to ensure that the results are sorted by the timestamp. This method is ok , but

I'm trying to compact (or at least merge) multiple databases, while stripping search records which are no longer required. Backstory: I've inherited the Cyrus IMAPd xapian-based search code from Greg Banks when he left Opera. One of the unfinished parts was removing expunged emails from the search database. We moved from having a single search database to supporting multiple