Making Postgres and Elasticsearch work together like it's 2023
Welcome to ZomboDB v3000.2.4. This is a minor bugfix release.
field_list
s during highlighting by @eeeebbbbrrrr in https://github.com/zombodb/zombodb/pull/891
Full Changelog: https://github.com/zombodb/zombodb/compare/v3000.2.3...v3000.2.4
Welcome to ZomboDB v3000.2.3. This is a minor bugfix release, fixing a small bug related to hit highlighting.
(a, b, c) w/2 d
now works when not all of the grouped terms exist in the document, by @eeeebbbbrrrr in https://github.com/zombodb/zombodb/pull/887
Full Changelog: https://github.com/zombodb/zombodb/compare/v3000.2.2...v3000.2.3
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.
Full Changelog: https://github.com/zombodb/zombodb/compare/v3000.2.1...v3000.2.2
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.
Full Changelog: https://github.com/zombodb/zombodb/compare/v3000.2.0...v3000.2.1
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.
fix issue #881 by @eeeebbbbrrrr in https://github.com/zombodb/zombodb/pull/882
Remove Postgres v11 support
[Fedora 35/36/37, Ubuntu Bionic, Ubuntu Kinetic]
[Fedora 39]
Full Changelog: https://github.com/zombodb/zombodb/compare/v3000.1.25...v3000.2.0
Full Changelog: https://github.com/zombodb/zombodb/compare/v3000.1.24...v3000.1.25
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.
Full Changelog: https://github.com/zombodb/zombodb/compare/v3000.1.23...v3000.1.24
Welcome to ZomboDB v3000.1.23. This is a bugfix release fixing various query execution and hit highlighting bugs.
fulltext_with_shingles
by @eeeebbbbrrrr in https://github.com/zombodb/zombodb/pull/865
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 https://github.com/zombodb/zombodb/pull/866
NOT
operator is now pushed down to linked fields ensuring the outer query evaluates the correct documents. by @eeeebbbbrrrr in https://github.com/zombodb/zombodb/pull/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: https://github.com/zombodb/zombodb/compare/v3000.1.22...v3000.1.23
This is ZomboDB v3000.1.22. It is a minor bugfix release related to index metadata discovery and hit highlighting.
zdb.field_mapping()
can now resolve named index links and nested object fields by @eeeebbbbrrrr in https://github.com/zombodb/zombodb/pull/858
zdb.highlight_document()
now properly handles the NULL
value in a query by @eeeebbbbrrrr in https://github.com/zombodb/zombodb/pull/860
zdb.highlight_document()
now properly handles the *
(MatchAll) wildcard in a query by @eeeebbbbrrrr in https://github.com/zombodb/zombodb/pull/862
zdb.default_replicas
and zdb.default_elasticsearch_url
GUCs can now be set via ALTER DATABASE ... SET ...
by @eeeebbbbrrrr in https://github.com/zombodb/zombodb/commit/8451cdc0702942a59e92ed388df5531e0d2785c6
Full Changelog: https://github.com/zombodb/zombodb/compare/v3000.1.21...v3000.1.22
Welcome to ZomboDB v3000.1.21. Primarily, it fixes an important crashing bug (at least) when CREATE INDEX ... USING zombodb
encounters an array that has at least one leading NULL value.
This bug has existed since v3000.1.15. We recommend all users upgrade immediately. A REINDEX is not required.
text[]
values with leading NULL elements can cause a crash or weird error https://github.com/zombodb/zombodb/issues/854 by @eeeebbbbrrrr in https://github.com/zombodb/zombodb/pull/855
match_none
. by @eeeebbbbrrrr in https://github.com/zombodb/zombodb/pull/856
Full Changelog: https://github.com/zombodb/zombodb/compare/v3000.1.20...v3000.1.21