summaryrefslogtreecommitdiff
path: root/textproc/xapian
AgeCommit message (Collapse)AuthorFilesLines
2013-06-04Update to 1.2.15. From the changelog:schmonz3-10/+10
Xapian-core 1.2.15 (2013-04-16): API: * QueryParser/TermGenerator: Don't include CJK codepoints which are punctuation in N-grams. * TermGenerator: Fix bug where we failed to generate the first bigram from the second sequence of N-grammable CJK characters in a piece of text. brass backend: * Call fdatasync()/fsync() when creating the "iambrass" file. chert backend: * Call fdatasync()/fsync() when creating the "iamchert" file. flint backend: * Call fdatasync()/fsync() when creating the "iamflint" file. tools: * delve: If -v is specified more than once, show even more info in some cases. Xapian-core 1.2.14 (2013-03-14): API: * MSet::get_document(): Don't cache retrieved Document objects unless they were requested with fetch(). This avoids using a lot of memory when many MSet entries are retrieved. (Fixes #604) matcher: * Check if a candidate document has at least the minimum weight needed before checking positional information, which speeds up slow phrase searches (partly addresses #394). brass backend: * Fix multipass compaction not to damage document values, and to merge the database stats correctly. (fixes #615) chert backend: * Fix multipass compaction not to damage document values, and to merge the database stats correctly. (fixes #615) flint backend: * Fix multipass compaction bug. (fixes #615) tools: * xapian-replicate: + Fix handling of delays between replication events - the subtraction of the target time and the current time was reversed, so we wouldn't sleep when before the deadline, but would sleep after it for the amount we'd missed it by. + On Microsoft Windows, we no longer sleep for more than 43 years if the target time for a replication event had already passed. (Fixes #472) Xapian-core 1.2.13 (2013-01-09): API: * TermGenerator: Add new method TermGenerator::set_max_word_length() to allow this limit to be adjusted by the user. * QueryParser: Implicitly close any unclosed brackets at the end of the query string. Patch from Sehaj Singh Kalra. * DateValueRangeProcessor: Add extra constructor overloaded form so that in DateValueRangeProcessor(1, "date:"), the const char * gets interpreted as std::string rather than bool. matcher: * Improved fix for #590 - count all matching LeafPostList objects with a Weight object rather than trying to prune at the MultiAndPostList level based on max_wt (if wdf is always zero for a term, BM25 gives max_wt of 0, which lead to us never counting that subquery. * Fix calculation of 0.0/0.0 in some cases. This then got used as a minimum weight, but it seems this gives -nan (at least on x86-64 Linux) so it may have been harmless in practice. * We no longer use the highest weighted MSet entry to calculate percentages, so remove code which finds it. brass backend: * Close excess file handles before we get the fcntl lock, which avoids the lock being released again if one is open on the lock file. Notably this avoids a situation where multiple threads in the same process could succeed in locking a database concurrently. chert backend: * Close excess file handles before we get the fcntl lock, which avoids the lock being released again if one is open on the lock file. Notably this avoids a situation where multiple threads in the same process could succeed in locking a database concurrently. flint backend: * Close excess file handles before we get the fcntl lock, which avoids the lock being released again if one is open on the lock file. Notably this avoids a situation where multiple threads in the same process could succeed in locking a database concurrently. remote backend: * Improve the UnimplementedError message for a MatchSpy subclass which doesn't implement name() so it's clearer that it is this particular subclass which can't be used remotely, rather than all MatchSpy objects. documentation: * valueranges.html: Update documentation to reflect change in Xapian 1.1.2 - DateValueRangeProcessor and StringValueRangeProcessor now support a prefix or suffix. * Clarify that the "reverse" parameter of set_sort_by_relevance_then_value() and set_sort_by_relevance_then_key() only affects the ordering of the value/key part of the sort. * docs/quickstart.html: Fix seriously outdated statement that Xapian doesn't create the database directory - that changed in 0.7.2 (released 2003-07-11). * HACKING: Try to make it clearer we're looking for a dual-licence on submitted patches. tools: * xapian-replicate: + Add a --full-copy option to force a full copy to be sent. (ticket#436) + Add --quiet option, and be a little more verbose by default. + Allow files > 32G to be be copied by replication. + Fix "if (fd > 0)" tests in some replication code to be "if (fd >= 0)". In practice this is unlikely to actually have caused problems since stdin is typically still open and using fd 0. + Simplify how we open the .DB file on the replication slave to just call open() once with O_CREAT, rather than once without, than stat() if that fails, and then again with O_CREAT|O_TRUNC if stat() doesn't show an ordinary file exists. examples: * quest: + New --flags command line option to allow setting arbitrary QueryParser flags. + Align option descriptions in --help output, and make the initial letter of such descriptions consistently lowercase.
2012-10-25Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.asau1-3/+1
2012-10-10Update to 1.2.12:wiz2-8/+9
Xapian-core 1.2.12 (2012-06-27): build system: * 1.2.11 had its library version information incorrectly set. This resulted in the shared library having an incorrect SONAME - e.g. on Linux, libxapian.so.21 instead of libxapian.so.22. This release has been made to fix this problem. documentation: * AUTHORS: Add the GSoC students. Xapian-core 1.2.11 (2012-06-26): API: * Add new QueryParser::STEM_ALL_Z stemming strategy, which stems all terms and adds a Z prefix. (Patch from Sehaj Singh Kalra, fixes ticket#562) * Add TermGenerator::set_stemming_strategy() method, with strategies which correspond to those of QueryParser. Based on patch from Sehaj Singh Kalra, with some tweaks for adding term positions in more cases. (Fixes ticket#563) * Correct "BM25Weight" to "TradWeight" in exception message from TradWeight. * We were failing to call init() for user-defined Weight objects providing the term-independent weight. These now get called with init(0.0). * Xapian::Auto::open_stub() now throws a Xapian::DatabaseOpeningError exception if the stub file can't be opened. Previously we failed to check for this condition, which resulted in us treating the file as empty. testsuite: * When the testsuite is using valgrind, we used to run remote servers under valgrind too (but with --tool=none) to get consistent behaviour as valgrind's emulation of x87 excess precision isn't exact. Now we only do this if x87 FP instructions are actually in use (which means x86 architecture and configure run with --disable-sse). * Make sure XAPIAN_MAX_CHANGESETS gets unset after replication testcases which set it, so further testcases don't waste time generating changesets. * Improved test coverage (including more tests for closed databases - ticket#337). brass backend: * After closing the database, methods which try to use the termlist would throw FeatureUnavailableError with message "Database has no termlist", assuming that the termlist table not being open meant it wasn't present. Fix to check if the postlist_table is open to determine which case we're in. chert backend: * After closing the database, methods which try to use the termlist would throw FeatureUnavailableError with message "Database has no termlist", assuming that the termlist table not being open meant it wasn't present. Fix to check if the postlist_table is open to determine which case we're in. inmemory backend: * Check if the database is closed in metadata_keys_begin() for InMemory Databases. build system: * xapian-config: Don't interpret a missing .la file as meaning that we only have static libraries. documentation: * Fix API documentation for Query constructors - both XOR and ELITE_SET can take any number of subqueries, not only exactly two. * Backport missing API documentation comments for operator++ and operator* methods or PositionIterator, PostingIterator and TermGenerator. * docs/replication.rst: Update documentation - since 1.2.5, the value of XAPIAN_MAX_CHANGESETS determines how many changesets we keep. * docs/admin_notes.rst: Correction - we don't "create a lock file", we "lock a file". * Fix API documentation for TradWeight constructor - "k1" should be "k". portability: * configure: Overhaul handling of compilers which pretend to be GCC. Clang is now detected, and we only pass it warning flags it actually understands. And we now check for symbol visibility support with Intel's compiler. * configure: Solaris automatically pulls in library dependencies, so set link_all_deplibs_CXX=no there. * configure: We now check -Bsymbolic-functions for all compilers. * configure: Enable -Wdouble-promotion for GCC >= 4.6. * Pass -ldl last when compiling zlib-vg.so, as that seems to be needed on Ubuntu 12.04. * Fix incorrect use of "delete" which should be "delete []". This is undefined behaviour in C++, though the type is POD, so in practice this probably worked OK on many platforms. * In BM25Weight when k1 or b is zero (not the default), we used to multiply an uninitialised double by zero, which is undefined behaviour, but in practice will often give zero, leading to the desired results. * xapian.h: Add check for Qt headers being included before us and defining 'slots' as a macro - if they are, give a clear error advising how to work around this (previously compilation would fail with a confusing error). Xapian-core 1.2.10 (2012-05-09): API: testsuite: * apitest: Extend tradweight1 to test that TradWeight(0) means that wdf and document length don't affect the weight of a term. * termgentest: Check that TermGenerator discards words > 64 bytes. matcher: * Don't count unweighted subqueries of MultiAndPostList in percentage calculations, as OP_FILTER maps to MultiAndPostList now. (ticket#590) brass backend: * When compacting, if the output database is empty, don't write out a metainfo tag. Take care not to divide by zero when computing the percentage size change for a table. chert backend: * When compacting, if the output database is empty, don't write out a metainfo tag. Take care not to divide by zero when computing the percentage size change for a table. documentation: * API documentation: + Note version when Database::close() was added. + Fix switched lower and upper in API documentation for Weight methods get_doclength_lower_bound() and get_doclength_upper_bound(). Correct maximum to minimum in get_doclength_lower_bound() comment and note that this excludes zero length documents. Fix "An lower" to "A lower". * docs/admin_notes.html: Mention that postlist and termlist tables also hold value info for chert. Mention that xapian-chert-update was removed in 1.3.0. Mention that you need to use copydatabase from 1.2.x to convert flint to chert. * HACKING: Update section on patches to mention git (git diff and git format-patch), and using "-r" with normal diff, and also that ptardiff offers a nice way to diff against an unpacked tarball. debug code: * Fix use of AssertEq() on NULL, which doesn't compile, at least with recent GCC. Xapian-core 1.2.9 (2012-03-08): API: * QueryParser: Fix FLAG_AUTO_SYNONYMS not to enable auto multi-word synonyms too (but in a different way to trunk so as to not break the ABI). matcher: * Fix issue with running AND, OR and XOR queries against a database with no documents in it - this was leading to a divide by zero, which led to MSet::get_matches_estimated() reporting 2147483648 on i386. build system: * Remove configure's --with-stlport and --with-stlport-compiler options, as they don't allow you to actually specify what you need to (at least to use the Debian STLport package), and instead document what to pass to configure to enable building with STLport (though it seems to no longer be actively maintained, and the debug mode (which is probably the most interesting feature now) doesn't seem to work on Debian stable). documentation: * Document that OP_ELITE_SET with non-term subqueries might pick subqueries which don't match anything. Closes ticket#49. * Document that you can define a static operator delete method in your subclass if deallocation needs to be handled specially. (Closes ticket#554) * Assorted minor documentation improvements. portability: * Address new warnings from GCC 4.6. * Fix argument order when linking xapian-check to fix mingw build. (ticket#567) * Add some missing explicit header includes to fix build with STLport.
2012-05-07Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=)dholland1-2/+2
It turns out there were a lot of these.
2012-01-10Indent.schmonz1-13/+13
2012-01-10Update to 1.2.8. From the changelog:schmonz5-64/+26
1.2.8: API: * Add support to TermGenerator and QueryParser for indexing and searching CJK text using n-grams. Currently this is only enabled when the environmental variable XAPIAN_CJK_NGRAM is set to a non-empty value. portability: + Some fixes for warnings when cross-compiling to mingw. * tests/soaktest/soaktest.cc: With Sun's compiler, random() and srandom() aren't in <cstdlib> so we need to use <stdlib.h> instead. 1.2.7: API: * Document objects now track whether any document positions have been modified so that replacing a modified document can completely skip considering updating positions if none have changed. Currently the flint, chert, and brass backends implement this optimisation. A common case this speeds up is adding and/or removing boolean filter terms to/from existing documents - for example this gives an 18% speedup for adding tags in notmuch. portability: * Fix -Wshadow warnings from GCC 4.6. * Fix warning from GCC 3.3. 1.2.6: API: * QueryParser: + Add new set_max_wildcard_expansion() method to allow limiting the number of terms a wildcard can expand to. (ticket#350) + If default_op is OP_NEAR or OP_PHRASE then disable stemming of the terms, since we don't index positional information for stemmed terms by default. * Spelling correction was failing to correctly handle words which had the same trigram in an even number of times. portability: * Fix to build for mingw. 1.2.5: API: * Enquire::get_eset() now accepts a min_wt argument to allow the minimum wanted weight to be specified. Default is 0, which gives the previous behaviour. * QueryParser: Handle NEAR/<offset> and ADJ/<offset> where offset isn't an integer the same way at the end of the query as in the middle. * Replication: + Only keep $XAPIAN_MAX_CHANGESETS changeset files when generating a new one (previously this variable only controlled if we generated changesets or not). Closes ticket#278. + $XAPIAN_MAX_CHANGESETS is reread each time, rather than only when the database is opened. + If you build Xapian with DANGEROUS mode enabled, changeset files now actually have the appropriate flag set (the reader will currently throw an exception, but that's better than quietly handling them incorrectly). portability: * api/compactor.cc: Add missing header <ctime> for time() (ticket#530). * api/compactor.cc: Use msvc_posix_rename() under __WIN32__ to atomically update stub file after compaction (ticket#525). * Fix uninitialised variable warnings with gcc -O3. * Eliminate std::string member of global static object used when compiled with --enable-log which was causes problems on Mac OS X. * Fix some issues highlighted by clang++ warnings. 1.2.4: API: * QueryParser: + Avoid a double free if Query construction throws an exception in a particular case. Fixes ticket#515. + Allow phrase generators between a probabilistic prefix and the term itself (e.g. path:/usr/local). + The correct window size wasn't being set in some cases when default_op was set to OP_PHRASE. * Enquire::get_mset(): + Avoid pointlessly trying to allocate lots of memory if the first document requested is larger than the size of the database. + An empty query now returns an MSet with firstitem set correctly - previously firstitem was always 0 in this case. * Document: Initialise docid to 0 when creating a document from scratch, as documented. * Compactor: + Move the database compaction and merging functionality into this new class, and make xapian-compact a simple wrapper around this class. (ticket#175) + Inputs can now be stub database directories or files, in which case the databases in the stub are used as inputs. + Add support for compacting to a stub database, which can be one of the inputs (for atomic update). + If spellings and/or synonyms were only present in some source databases, they weren't copied to the output database, but now they are. portability: * configure: Add support for --enable-sse=sse and --enable-sse=sse2 to allow control of which SSE instructions to use. * configure: Enable use of SSE maths on x86 by default with Sun's compiler. * configure: Beef up the test for whether -lm is required and add a special case to force it to be for Sun's C++ compiler - there's some interaction with libtool and/or shared objects which means that the previous configure test didn't think -lm is needed here when it is. * Fix to build on OpenBSD 4.5 with GCC 3.3.5. * Need to avoid excess precision on m68k when targeting models 68010, 68020, 68030 as well as 68000. * Fix compilation with Sun's C++ compiler. * Fix testsuite to build on Solaris < 10. 1.2.3: API: * Database::get_spelling_suggestion() will now suggest a correction even if the passed word is in the dictionary, provided the correction has at least the same frequency. Partly addresses #225. * QueryParser: + Fix handling of groups of terms which are all stopwords - in situations where this causes a problem we now disable stopword checks for such groups. (ticket#245) + Fix to be smarter about handling a boolean filter term containing ".." in the presence of valuerangeprocessors. portability: * configure: Don't pass -mtune=generic unless GCC >= 4.2 is in use (ticket#492). * Fix handling of some obscure cases of resolving relative paths on Microsoft Windows. (ticket#243). * Optimise closing of all unwanted file descriptors after forking by using closefrom() if available, and otherwise providing our own implementation (optimised to some extent for many platforms). * Fix test harness to build under Microsoft Windows (ticket#495). 1.2.2: portability: * Revert 1.2.1 change to visibility of Xapian::Weight's copy constructor as it making it private broke compilation with GCC 4.1 (which seems to be a bug in this compiler version). * tests/harness/testsuite.cc: Need <cstdio> for sprintf(). Fixes compilation error which was masked if valgrind was installed. (ticket#489) pkgsrc changes: * Remove options (the "quartz" backend was unrelated to Darwin and no longer exists). * Unconditionally buildlink libuuid. If that's overzealous, improve its builtin detection.
2011-12-03Add devel/libuuid buildlink on Linux and SunOS only.sbd2-2/+18
Bump PKGREVISION
2011-11-26Fix build with newer GCCjoerg2-1/+14
2010-12-03Updated textproc/xapian to 1.2.2abs5-73/+97
tested on NetBSD 5.x amd64 changelog since 1.0.18 runs to 64k with no obvious highlights.
2010-02-16Update to 1.0.18:wiz3-8/+73
Xapian-core 1.0.18 (2009-02-14): API: * Document: Add new add_boolean_term() method, which is an alias for add_term() with wdfinc=0. * QueryParser: + Add support for quoting boolean terms so they can contain arbitrary characters (partly addresses ticket#128). + Add ENCLOSING_MARK and COMBINING_SPACING_MARK categories, plus several zero-width space characters, as phrase generators. This mirrors a better fix in 1.1.4, but without losing compatibility with existing databases. + Fix handling of an explicit AND before a hated term (foo AND -bar). (ticket#447) * TermIterator: Only include trailing '+' or '#' on a term if it isn't followed by a word character (makes more sense and matches QueryParser's behaviour). (ticket#446) * Database: Fix many methods to behave better on a database with no subdatabases, such as is constructed by Database(). Fixes ticket#415. testsuite: * Add test coverage for xapian-compact, and improve coverage for WritableDatabase::replace_document(). * apitest: Rename matchfunctor<n> to matchdecider<n> to match current terminology. flint backend: * When updating documents, don't update posting entries which haven't changed. Largely fixes ticket #250. * If the number of entries in the position table happened to be 4294967296 or an exact multiple, Xapian would ignore positional data for that table when running queries. * Iterating all the terms in the database with a prefix is now slightly more efficient. * Fix locking code to work if stdin and/or stdout have been closed. * If a document is replaced with itself unmodified, we no longer increase the automatic flush counter. * When iterating a posting list modified since the last flush(), the reported wdf is now correct (previously it was too high by its old value). * Replacing a document deleted since the last flush failed to update the collection frequency and wdf, and caused an assertion failure when assertions were enabled. * WritableDatabase::replace_document() didn't always remove old positional data (the only effect is that the position table was bloated by unwanted entries). * xapian-inspect: + New "until" command which shows entries until a specified key is reached. + New "open" command which allows easy switching between tables. * xapian-compact: Fix typos in --help output. quartz backend: * Replacing a document deleted since the last flush failed to update the collection frequency and wdf, and caused an assertion failure when assertions were enabled. * WritableDatabase::replace_document() didn't always remove old positional data (the only effect is that the position table was bloated by unwanted entries). remote backend: * Throw UnimplementedError if a MatchDecider is used with the remote backend. Previously Xapian returned incorrect results in this case. build system: * configure: With --enable-maintainer-mode, enable -Werror for GCC >= 4.1 rather than >= 4.0 as Apple's GCC 4.0 gives bogus uninitialised variable warnings. documentation: * The API documentation now includes Xapian::Error and subclasses, and doesn't mention Xapian::Query::Internal. * Make clear in the Xapian::Document API documentation that this class is a lazy handle and discuss the issues this can cause. * INSTALL: Improve text about zlib dependency. * HACKING: Add details of our licensing policy for accepting patches. examples: * quest: If no database is specified, still parse the query and report Query::get_description() to provide an easy way to check how a query parses. portability: * Fix GCC 4.2 warning. xapian-core 1.0.17 (2009-11-18): API: * QueryParser: + Fix handling of a group of two or more terms which are all stopwords which notably caused issues when default_op was OP_AND, but could probably manifest in other cases too. Fixes ticket#406. + Fix interaction of FLAG_PARTIAL and FLAG_SYNONYM. (ticket#407) * Database: A database created via the default constructor no longer causes a segfault when the methods get_metadata() or metadata_keys_begin() are called. flint backend: * Don't try to close the fd one more than the maximum allowable when locking the database. Harmless, except it causes a warning when running under valgrind. (ticket#408) remote backend: * Xapian::Sorter isn't supported with the remote backend so throw UnimplementedError rather than giving incorrect results. (ticket#384) * Fix potential reading off the end of the MSet which is returned internally by the remote server. documentation: * Various documentation comment improvements for the Database class. examples: * examples/quest.cc: Tighten up the type of the error we catch to detect an unknown stemming language. portability: * xapian-config: Need to quote ^ for Solaris /bin/sh. * configure: Actually use any flags we determine are needed to switch the compiler to proper ANSI C++ mode, when building xapian-core - this stopped working in 1.0.12, breaking support for HP's aCC, Compaq's cxx, Sun's CC, and SGI's CC.
2009-11-24Provide a stringise function for 64bit integers, so that xapian willagc3-1/+47
build on systems with 64bit time_t's.
2009-09-10Update to 1.0.16. From the changelog:schmonz2-7/+7
flint backend: * Fix a typo which stopped this fix in 1.0.12 from working (ticket #398): If we fail to get the lock after we spawn the child lock process (the common case is because the database is already open for writing) then we now clean up the child process properly. documentation: * Improve API documentation of QueryParser::set_default_op() and QueryParser::get_default_op(). portability: * Fix build failure on Mac OS X 10.6.
2009-08-27Update to 1.0.15. From the changelog:schmonz3-46/+15
flint backend: * Backport the lazy update changes from 1.1.2: WritableDatabase::replace_document() now updates the database lazily in simple cases - for example, if you just change a document's values and replace it with the same docid, then the terms and document data aren't needlessly rewritten. Caveats: currently we only check if you've looked at the values/terms/data, not if they've actually been modified, and only keep track of the last document read. * Fix PostingIterator::skip_to() on an unflushed WritableDatabase to skip documents which were added and deleted since the last flush. (ticket#392) documentation: * Overhaul the doxygen options we use and tweak various documentation comments to improve the generated API documentation. * Explicitly document that an empty prefix argument to QueryParser::add_prefix() means "no prefix". * Update the documentation comments for Enable::set_sort_by_value(), set_sort_by_value_then_relevance(), and set_sort_by_relevance_then_value() to mention sortable_serialise() as a good way to store numeric values for sorting.
2009-07-23Update to 1.0.14. From the changelog:schmonz2-7/+7
API: * When using more than one ValueRangeProcessor, QueryParser didn't reset the begin and end strings to ignore any changes made by a ValueRangeProcessor which returned false, so further ValueRangeProcessors would see any changes it had made. This is now fixed, and test coverage improved. flint backend: * Use F_FULLFSYNC where available (Mac OS X currently) to ensure that changes have been committed to disk. (ticket#288) remote backend: * Fix handling of percentage weights in various cases when we're searching multiple remote databases or a mix of local and remote databases.
2009-07-18Update to 1.0.13. From the changelog:schmonz2-7/+7
API: * Xapian::Document no longer ever stores empty values explicitly. This wasn't intentional behaviour, and how this case was handled wasn't documented. The amended behaviour is consistent with how user metadata is handled. This change isn't observable using Document::get_value(), but can be noticed when iterating with Document::values_begin(), using Document::values_count(), or trying to delete the value with Document::remove_value(). matcher: * If a query contains a MatchAll subquery, check for it before checking the other terms so that the loop which checks how many terms match can exit early if they all match. * When an OR or ANY_MAYBE decayed to an AND, we were carefully swapping the children for maximum efficiency, but the condition was reversed so we were in fact making things worse. This was noticed because it was resulting in the same query running faster when more results were asked for! * Only build the termname to termfreq and weight map for the first subdatabase instead of rebuilding it for each one. Also don't copy this map to return it. This should speed up searches a little, especially those over multiple databases. * If a submatcher fails but ErrorHandler tells us to continue without it, we just use a NULL pointer to stand in rather than allocating a special dummy place-holder object. * Remove AndPostList, in favour of MultiAndPostList. AndPostList was only used as a decay product (by AndMaybePostList and OrPostList), and doesn't appear to be any faster. Removing it reduces CPU cache pressure, and is less code to maintain. * Call check() instead of skip_to() on the optional branch of AND_MAYBE. flint backend: * Fix a bug in TermIterator::skip_to() over metadata keys. remote backend: * Fix xapian-tcpsrv --interface option to work on MacOS X (ticket#373). * Fix typo which caused us to return the docid instead of the maximum weight a document from a remote match could return! This could have led to wrong results when searching multiple databases with the remote backend, but probably usually didn't matter as with BM25 the weights are generally small (often all < 1) while docids are inevitably >= 1. inmemory backend: * The inmemory backend doesn't support iterating over metadata keys. Trying to do so used to give an empty iteration, but has now been fixed to throw UnimplementedError (and this limitation has now been documented). documentation: * INSTALL: We no longer regularly test build with GCC 2.95.4 and we're raising the minimum GCC version required to 3.1 for Xapian 1.1.x. * Document what passing maxitems=0 to Enquire::get_mset() does. * docs/queryparser.html: Add examples of using a prefix on a phrase or subexpression. * Correct doxygen comments for user metadata functions: Database::get_metadata() throw UnimplementedError but WritableDatabase::set_metadata() can. * Document that Database::metadata_keys_begin() returns an end iterator if the backend doesn't support metadata. * HACKING: Update the list of Debian/Ubuntu packages needed for a development environment.
2009-07-07user-destdir supportjoerg1-1/+3
2009-06-14Remove @dirrm entries from PLISTsjoerg1-5/+1
2009-04-20Update to 1.0.12. From the changelog:schmonz3-37/+11
* WritableDatabase::remove_spelling() now works properly. * The QueryParser now treats NON_SPACING_MARK Unicode characters as phrase generators, which improves handling of Arabic. This is a stop-gap solution for 1.0.x which will work with existing databases without requiring reindexing - in 1.1.0, NON_SPACING_MARK will be regarded as part of a word. (ticket#355) * Fix undefined behaviour in distribution of OP_NEAR and OP_PHRASE over a non-leaf subquery (indentified by valgrind on testcase nearsubqueries1). (ticket#349) * Enhance distribution of OP_NEAR/OP_PHRASE over non-leaf subqueries to work when there are multiple non-leaf subqueries (ticket#201). * Enquire::get_mset() no longer needlessly checks if the documents exist. * PostingIterator::get_description() output improved visually in some cases. * Enquire::get_mset(): + Now throws UnimplementedError if there's a percentage cutoff and sorting is primarily by value - this has never been correctly supported and it's better to warn people than give incorrect results. + No longer needlessly copies the results internally. + When searching multiple databases, now recalculates the maximum attainable weight after each database which may allow it to terminate earlier. (ticket#336). + Fix inconsistent percentage scores when sorting primarily by value, except when a MatchDecider is also being used; document this remaining problem case. (ticket#216) * Enquire::set_sort_by_value() (and similar methods): Rename the wrongly named "ascending" parameter to "reverse", and note that its value should always be explicitly given since defaulting to "reverse=true" is confusing and the default will be deprecated in 1.1.0. (ticket#311) * Database::allterms_begin(): Fix memory leak when iterating all terms from more than one database. * Query::get_terms_begin(): Don't return "" from the TermIterator (happened when the query contained or was Query::MatchAll). * Add QueryParser::FLAG_DEFAULT to make it easier to add flags to those set by default.
2009-03-20Simply and speed up buildlink3.mk files and processing.joerg1-13/+6
This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-01-21Add xapian-flint-backend and xapian-quartz-backend options, allowingdsainty2-14/+36
rationalisation of backends (and also allows wiring the database to the older database format if desired). The "suggested options" select support for both formats, which is also the status quo.
2009-01-08Buildlink in the required devel/zlib. Fixes build on systems where native ↵dsainty1-1/+2
zlib (header) is not installed.
2009-01-07Update to 1.0.10:wiz2-7/+7
Xapian-core 1.0.10 (2008-12-23): API: * Composing an OP_NEAR query with two non-term subqueries now throws UnimplementedError instead of AssertionError (in a --enable-assertions build) or leading to unexpected results (otherwise). This partly addresses bug#201. * Using a MultiValueSorter with no values set no longer causes a hang or segmentation fault (but it is still rather pointless!) matcher: * If we're using values for sorting and for another purpose, cache the Document::Internal object created to get the value for sorting, like we do between other uses. flint backend: * If the disk became full while flushing database changes to disk, the WritableDatabase object would throw a DatabaseError exception but be left in an inconsistent state such that further use could lead to the database on disk ending up in a "corrupt" state (theoretically fixable, but no tool to fix such a database exists). Now we try to ensure that the object is left in a consistent state, but if doing so throws a further exception, we put the WritableDatabase object in a "closed" state such that further attempts to use it throw an exception. * Create the lockfile "flintlock" with permissions 0666 so that the umask is honoured just like we do for the other files (previously we used 0600). Previously it wasn't possible to lock a database for update if it was owned by another user, even if you otherwise had sufficient permissions via "group" or "other". * Fix garbled exception message when a base file can't be reread. quartz backend: * Fix garbled exception message when a base file can't be reread. remote backend: * xapian-tcpsrv and xapian-progsrv now accept -w as a short form of --writable, as was always intended. build system: * This release now uses newer versions of the autotools (autoconf 2.62 -> 2.63; automake 1.10.1 -> 1.10.2). documentation: * INSTALL: Add new paragraphs about HP's aCC and IRIX (adapted from footnotes in PLATFORMS). * PLATFORMS: HP testdrive has been shut down, so all mark all those machines as "no longer available". Update atreus' build report to 1.0.10. * docs/queryparser.html: Add link to valueranges.html. examples: * delve: Add missing "and" to --help output. Report termfreq and collection freq for each term we're asked about. portability: * Fix to build with GCC 4.4 snapshot. Xapian-core 1.0.9 (2008-10-31): API: * Database::get_spelling_suggestion() is now faster (15% speed up for parsing queries with FLAG_SPELLING_CORRECTION set in a test on real world data). * Fix OP_ELITE_SET segmentation fault due to excess floating point precision on x86 Linux (and possibly other platforms). * Database::allterms_begin() over multiple databases now gives a TermIterator with operations O(log(n)) rather than potentially O(n) in the number of databases. * Add new Database methods metadata_keys_begin() and metadata_keys_end() to allow the complete list of metadata in a database to be retrieved (this API addition is needed so that copydatabase can copy database metadata). testsuite: * Remove the cached test databases before running the testsuite. * apitest: Fix cursordelbug1 to work on Microsoft Windows (bug#301). * apitest,queryparsertest: Skip tests which fail because the timer granularity is too coarse to measure how long the test took. In practice, this is only an issue on Microsoft Windows (bug#300 and bug#308). matcher: * Adjust percent cutoff calculations in the matcher in a way which corresponds to the change to percentage calculations made in 1.0.7 to allow for excess precision. * Query::MatchAll no longer gives match results ranked by increasing document length. flint backend: * xapian-compact: Fix crash while compacting spelling table for a single database when built with MSVC, and probably other platforms, though Linux got lucky and happened to work (bug#305). build system: * configure: Disable -Wconversion for now - it's not useful for older GCC and is buggy in GCC 4.3. * configure: Set -Wstrict-overflow to 1 instead of 5, to avoid unreasonable warnings under GCC 4.3. documentation: * Minor improvements to API documentation, including documenting the XAPIAN_FLUSH_THRESHOLD environmental variable in WriteableDatabase::flush() (bug#306). * valueranges.html: Fix typos in example code, and drop superfluous empty destructor from ValueRangeProcessor subclass. * HACKING: Several improvements. examples: * copydatabase: Also copy user metadata. Xapian-core 1.0.8 (2008-09-04): API: * Fix output of RSet::get_description testsuite: * Report subtotals per backend, rather than per testgroup per backend to make the output easier to read. flint backend: * Fix WritableDatabase::add_document() and replace_document() not to be O(n*n) in the number of values in the new document. * Fix handling of a table created lazily after the database has had commits, and which is then cursored while still in sequential mode. * Fix failure to remove all the Btree entries in some cases when all the postings for a term are removed. (bug#287) * xapian-inspect: Show the help message on start-up. Correct the documented alias for next from ' ' to ''. Avoid reading outside of input string when it is empty. (bug#286) quartz backend: * Backport fix from flint for WritableDatabase::add_document() and replace_document() not to be O(n*n) in the number of values in the new document. build system: * configure: Report bug report URL in --help output. * xapian-config: Report bug report URL in --help output. * configure: Fix deprecation error for --enable-debug=full to say to instead use '--enable-assertions --enable-log' not '--enable-debug --enable-log'. documentation: * valueranges.html: Expand on some sections. examples: * quest: Fix to catch QueryParserError instead of const char * which QueryParser threw in Xapian < 1.0.0. * copydatabase: Use C++ forms of C headers. Only treat '\' as a directory separator on platforms where it is. Update counter every 13 counting up to the end so that the digits all "rotate" and the counter ends up on the exact total. portability: * Eliminate literal top-bit-set characters in testsuite source code.
2008-07-26Initial import of Xapian, an Open Source Search Engine Library,schmonz5-0/+423
released under the GPL. It's written in C++, with bindings to allow use from Perl, Python, PHP, Java, Tcl, C# and Ruby (so far!) Xapian is a highly adaptable toolkit which allows developers to easily add advanced indexing and search facilities to their own applications. It supports the Probabilistic Information Retrieval model and also supports a rich set of boolean query operators. If you're after a packaged search engine for your website, you should take a look at Omega: an application we supply built upon Xapian. Unlike most other website search solutions, Xapian's versatility allows you to extend Omega to meet your needs as they grow.