github weaviate/weaviate 0.22.3
0.22.3 - Bugfixes and Vector as part of Object's Meta

latest releases: v1.25.1, v1.24.14, v1.23.15...
4 years ago

Docker image/tag: semitechnologies/weaviate:0.22.3
See also: example docker compose files in english and dutch.

Breaking Changes

none

New Features

  • Return objects' vector position when meta=true (#1041)
    As part of the classification feature a meta option (passed as a query parameter) was added to the GET /v1/things and GET /v1/actions API. If the object was part of a classification, meta information about that classification is printed. Additionally, the meta object will now - regardless of classifications - also contains the objects vector position.

    Keep in mind that the 600-dimensional vector is about 2.4KB of size in the underlying storage and about twice that size when encoded as float numbers in json. So you will add about 5KB of data per object when setting meta=true. While this is negligible on single objects, the additional data to be transferred on long list queries might add up to a lot of additional traffic. So, only set this option if really necessary.

Fixes

  • Bug: ?meta=true ignored on list queries (#1099)
    Prior to this release setting the meta=true query param worked on GET /v1/things/{id} (single object), but not on GET /v1/things (list of objects). This releases fixes this and makes sure meta=true can now be set on both types of GET queries

  • Bug: Numbers and other characters lead to error in /c11y/concepts endpoint (#1078)
    The requirements for class names and other schema fields have been loosened in the past. As of now any utf-8 letter or digit is an acceptable character. However, the /c11y/concepts endpoint. which can be used to inspect word concepts in the contextionary space, still validated a strict [A-Za-z]. This has been changed and now all utf-8 letters and digits are acceptable.

Don't miss a new weaviate release

NewReleases is sending notifications on new releases.