v3000.2.5

Welcome to ZomboDB v3000.2.5. This is a minor bugfix release that fixes an issue where ZomboDB's query rewriting hooks didn't know about the relatively new Postgres Memoize node, causing certain query plans to raise an ERROR during execution.

What's Changed

• Issue 895 by @eeeebbbbrrrr in #897
• Re-enable alpine builds by @kingjan1999 in #894

New Contributors

• @kingjan1999 made their first contribution in #894

Full Changelog: v3000.2.4...v3000.2.5

v3000.2.4

Welcome to ZomboDB v3000.2.4. This is a minor bugfix release.

What's Changed

• fix issue #889: Properly expand index field_lists during highlighting by @eeeebbbbrrrr in #891

Full Changelog: v3000.2.3...v3000.2.4

v3000.2.3

Welcome to ZomboDB v3000.2.3. This is a minor bugfix release, fixing a small bug related to hit highlighting.

What's Changed

• issue #886 - highlighting (a, b, c) w/2 d now works when not all of the grouped terms exist in the document, by @eeeebbbbrrrr in #887

Full Changelog: v3000.2.2...v3000.2.3

v3000.2.2

This is ZomboDB v3000.2.2. It is a minor bugfix release fixing an issue with the zdb.highlight_document() function not properly highlighting matches against the ZQL /TO/ range operator.

What's Changed

• fix issue #884 by @eeeebbbbrrrr in #885

Full Changelog: v3000.2.1...v3000.2.2

v3000.2.1

Welcome to ZomboDB v3000.2.1. This is a minor release that resolves an ERROR when trying to highlight non-text fields with a NULL value when using a range operator like >= or <. It's a followup fix to issue #807 from March 2023.

What's Changed

• Follow up fix for #807 by @eeeebbbbrrrr in #883

Full Changelog: v3000.2.0...v3000.2.1

v3000.2.0

Welcome to ZomboDB v3000.2.0.

This is a "major" release in that it removes support for Postgres 11. pg11 EOL'd back in November 2023.

There's also an important bugfix in this release that fixes a problem with inadvertently updating a row multiple times if the containing table has one or more shadow=true indexes. Further, updating a document twice within the same transaction could then cause both versions to appear live in the index due to ZDB updating each instance twice.

Depending on your usage patterns you may have seen the user-facing result of this, which is that certain aggregate queries such as zdb.terms() or zdb.tally() include terms from the old and new versions of the same row.

The fix for this bug does not itself necessitate a REINDEX. However, if your backing index exhibits problems that might have stemmed from this bug then at least those affected records need to be updated (a "no-op" update would be fine). Worst case, yes, a full REINDEX (or VACUUM FULL) for the entire table.

What's Changed

• fix issue #881 by @eeeebbbbrrrr in #882

  • there were some old references to pg10 that were removed too

• Remove Postgres v11 support

  • remove binary artifacts for: [Fedora 35/36/37, Ubuntu Bionic, Ubuntu Kinetic]
  • add binary artifacts for [Fedora 39]

Full Changelog: v3000.1.25...v3000.2.0

v3000.1.25

What's Changed

• Add TLS support in Elasticsearch client by @mwieczorkiewicz in #874
• Fix issue #876 by @eeeebbbbrrrr in #877

New Contributors

• @mwieczorkiewicz made their first contribution in #874

Full Changelog: v3000.1.24...v3000.1.25

v3000.1.24

Welcome to ZomboDB v3000.1.24. Yet another bugfix release.

This release fixes a bug where a VACUUM against a table with a USING zombodb index might cancel itself depending on if Postgres (or you) decided to use "parallel vacuum", which is the default.

What's Changed

• Fix issue #869 by @eeeebbbbrrrr in #870

Full Changelog: v3000.1.23...v3000.1.24

v3000.1.23

Welcome to ZomboDB v3000.1.23. This is a bugfix release fixing various query execution and hit highlighting bugs.

What's Changed

• Fix issue #863 - Long-tail phrases are now properly highlighted when the underlying field analyze is ZDB's fulltext_with_shingles by @eeeebbbbrrrr in #865
• Fix issue #864 - the WITH operator now properly works with what are essentially fake "object" fields -- fields that come from a named index link that's used in a view with a shadow index by @eeeebbbbrrrr in #866
• Fix issue #867 -- the unary NOT operator is now pushed down to linked fields ensuring the outer query evaluates the correct documents. by @eeeebbbbrrrr in #868

The fix for #867 also brings more sophisticated linked field groupings. When a zdb.tally()-style aggregate function is used and is returning a field from a view while the query queries fields in a linked index, ZDB now reduces the number of ES queries necessary to solve the query to the bare minimum. It is believed that in such a scenario, query performance will be measurably faster.

Full Changelog: v3000.1.22...v3000.1.23

v3000.1.22

This is ZomboDB v3000.1.22. It is a minor bugfix release related to index metadata discovery and hit highlighting.

What's Changed

• fix issue #857 - zdb.field_mapping() can now resolve named index links and nested object fields by @eeeebbbbrrrr in #858
• fix Issue #859 - zdb.highlight_document() now properly handles the NULL value in a query by @eeeebbbbrrrr in #860
• fix issue #861 - zdb.highlight_document() now properly handles the * (MatchAll) wildcard in a query by @eeeebbbbrrrr in #862
• impl issue #851 - the zdb.default_replicas and zdb.default_elasticsearch_url GUCs can now be set via ALTER DATABASE ... SET ... by @eeeebbbbrrrr in 8451cdc

Full Changelog: v3000.1.21...v3000.1.22