weaviate/weaviate v1.9.1

v1.9.1 - Plenty of bug fixes, including for "conflicting modules"

on GitHub

Breaking Changes

none

New Features

none

Fixes

• Allow running "conflicting" modules in the same setup (#1744)

  Prior to this release, Weaviate would not start up if multiple modules would try to provide the same search operators, such as nearText. For example text2vec-contextionary and text2vec-transformers could not run in the same setup. The reason for this was that Explore{} which would search across classes would not be able to handle incompatible vector spaces. This release makes sure that the provided search operator belongs to the configured vectorizer. In turn, cross-class searching across incompatible vector spaces such as using Explore {} will be deactivated if conflicting modules are present.

• Grouping by ref prop leads to error (#1778)

  Thanks to Alex Cannan for discovering this

• Delete fails on multi-node setup (#1780)

  Thanks to ayoub louati for discovering this.

• Bug: Querying Date attributes fail when sharding (#1775)

  Thanks to @zoltan-fedor for discovering this

• where filter with 2 Anded Like clauses and a nearText filter causes weaviate to panic. (#1772)

  Thanks to @StefanBogdan for discovering this

• PATCH (merge) fails on multi-node cluster (#1781)

  Thanks to @zoltan-fedor for discovering this

• Bug: Chained filter finds results when it shouldn't since v1.8.0 (#1770)

  Thanks to Pranav Pawar for discovering this

• Bug: (another) potential data race in compaction logic (#1762)

• [Bug] Limit removes viable results when data has been previously deleted (#1765)

  Thanks to @ywchan2005 for your help in investigating this