From 502922f6bce018255b16e0c8953e3deb73aa3e84 Mon Sep 17 00:00:00 2001 From: Olly Betts Date: Thu, 23 Jun 2022 17:49:58 +1200 Subject: [PATCH] Update NEWS from git log --- xapian-applications/omega/NEWS | 81 ++++++++++++++++++++++++++++++++++++ xapian-bindings/NEWS | 44 +++++++++++++++++++- xapian-core/NEWS | 93 ++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 217 insertions(+), 1 deletion(-) diff --git a/xapian-applications/omega/NEWS b/xapian-applications/omega/NEWS index a1b338f3b..03d3dd92f 100644 --- a/xapian-applications/omega/NEWS +++ b/xapian-applications/omega/NEWS @@ -1,3 +1,84 @@ +up to: 303e01feb1af9d5cc4ed46696c8893ca0cab0cfb + +Omega 1.4.20 (2022-06-23): + +general: + +documentation: + +indexers: + +* omindex: + + + OpenDocument: Previously we only inserted an implicit space before each + paragraph. Now we insert them both before and after each paragraph and + heading, and before forced each line-break and tab. + + + Add extension mapping for .awt (Abiword templates). + + + Index metadata from XPS files. + + + Remove lingering handling for database backends without slot bounds since + all backends have been required to support these since 1.4.11. + +* scriptindex: + + + Process an incomplete final line from a dump file. Previously if the final + line lacked a newline scriptindex would quietly ignore it (unless it was + the only line). + + + The `unique` action now takes an optional `missing` parameter to specify + what to do if a record doesn't trigger the unique action or triggers it + with an empty value. The default is now to issue a warning and create a + new document (the same as before, except that there was only previously a + warning for the empty value case). In Omega 1.5.0 the default will change + to an error as that seems a better default, but is less compatible with + potential existing use. + + + If we hit an error while parsing the index script we used to exit right + away, but now we finish parsing the index script since it's more helpful to + report all the errors in an index script rather than the user having to + fix them one by one. This requires us to sensibly recover after each index + script parse error - if you find a case where this recovery triggers + further bogus errors please report it and we'll try to improve the + recovery. + + + In four cases while handling input data (two cases of bad hex data fed + to `hextobin`, an input data line without a `=`, and `load` failing to + load the specified file) we'd emit a diagnostic that was labelled as an + "error" but really it was handled as a warning as we kept reading input + and the "error" didn't affect the exit status. It doesn't really make + sense to continue in any of these cases so we now exit with non-zero status + right away. + + + A parameter in the index script which should be an integer but isn't, or + should be positive but isn't now gives an error rather than a warning since + an error seems more helpful. + + + All diagnostics issued while parsing the index script now include column + information. + + + Avoid forcibly flushing the output stream after every message. + +omega: + +templates: + +testsuite: + +* Improve test coverage for scriptindex. + +build system: + +portability: + +* Require PCRE2 instead of PCRE. The original PCRE is now EOL and unmaintained + (last release was June 2021). In omega it's potentially used to process + input from the internet, so security is a real concern hence we're switching + to PCRE2. + +packaging: + Omega 1.4.19 (2021-12-31): documentation: diff --git a/xapian-bindings/NEWS b/xapian-bindings/NEWS index b4d07853a..4f9d1cdd2 100644 --- a/xapian-bindings/NEWS +++ b/xapian-bindings/NEWS @@ -1,3 +1,45 @@ +up to: f7300f204c0cb9bb0e0e3a67657b70a1d7e3d26b + +Xapian-bindings 1.4.20 (2022-06-16): + +Documentation: + +General: + +* Enable -fvisibility-inlines-hidden option if the compiler supports it. + +Packaging: + +Portability: + +CSharp: + +Java: + +Lua: + +Perl: + +PHP: + +PHP7: + +* Add missing reference tracking. XapianEnquire now keeps a reference to the + current XapianSorter object (if any). XapianQueryParser now keeps a + reference to any set XapianFieldProcessor objects. Test coverage for keeping + references to set functor objects is now more comprehensive. + +* smoketest.php: Remove bogus extra null parameters. PHP ignores these extra + parameters, but it's more helpful to be testing valid usage. + +Python: + +Python3: + +Ruby: + +Tcl: + Xapian-bindings 1.4.19 (2021-12-31): Documentation: @@ -15,7 +57,7 @@ General: Perl: * Add missing wrappers for some QueryParser FLAG_* constants. - + * Fix incorrect formatting in the processed POD documentation due to missing escaping of `>` in code snippets. diff --git a/xapian-core/NEWS b/xapian-core/NEWS index 8b6649666..9399a6e70 100644 --- a/xapian-core/NEWS +++ b/xapian-core/NEWS @@ -1,3 +1,96 @@ +up to: 1955d225c505eb6ca0811030fb7cf53ac79277d3 + +Xapian-core 1.4.20 (2022-06-16): + +API: + +* Throw DatabaseNotFoundError when the database directory doesn't exist or + when it doesn't contain a Xapian database. Patch from Germán Méndez Bravo + in https://github.com/xapian/xapian/pull/258 + +* Improve exception message for attempting to remove an empty term (the + exception type is still InvalidArgumentError). Reported by David Bremner. + +testsuite: + +* Reenable commented out queryparser testcase. The FIXME comment said "This + throws an exception as of 1.3.6, but once implemented we should re-enable it" + - it now passes so it seems this has since been implemented. + +* Expand some query-related testcases. + +matcher: + +* Optimise when a value range is a superset of the slot bounds but the value + slot frequency is not equal to the document count by replacing the lower + bound with an empty string to make the bounds check very cheap. + +* Avoid creating a PostList tree for an empty shard. This avoids pointless + work in an uncommon case, but also by handling this up front the code in + PostList subclasses for query operators can assume the shard isn't empty + which simplifies the code in several places. + +* Remove lingering handling for database backends without slot bounds since + all backends have been required to support these since 1.4.11. + +* Fix collection frequency estimates for positional operators. This affects + the weighting of positional operators in subqueries of OP_SYNONYM with + weighting schemes which use the collection frequency. + +glass backend: + +* xapian-check: Test decompress data in the spelling and synonym tables. + We don't have structure checking for these tables, but we can at least fetch + each entry and check for decompression problems. + +* Improve error if block overwritten in WritableDatabase. Drop "are there + multiple writers?" as it's rarely a useful question to ask since we started + using fcntl() locking as it's now very hard to get multiple concurrent + writers on a database. Instead suggest running xapian-check, which is + probably the best next step for a user who hits this problem. + +chert backend: + + +remote backend: + + +inmemory backend: + + +build system: + + +documentation: + +* Document precedence of NEAR and ADJ. + +* INSTALL: Note that MSVS 2022 works. + +tools: + +* quest: Add --freqs option to show term frequencies. + +* xapian-delve -v: Show value slot bounds and freq + +examples: + + +portability: + +* Fix to build with a C++20 compiler. + +* configure now probes for a declaration of strerror_r() before using it, since + a declaration is required in C++ code. + +* MSVC: Use intrinsics to implement addition with overflow check. + +packaging: + + +debug code: + + Xapian-core 1.4.19 (2021-12-31): API: -- 2.11.4.GIT