« Changelog History


Weaviate v0.22.5 Release Notes

Release Date: 2020-04-01 // about 4 years ago

  • 🐳 Docker image/tag: semitechnologies/weaviate:0.22.5
    👀 See also: example docker compose files in English, German, Dutch, Italian and Czech.

    💥 Breaking Changes

    none

    🆕 New Features

    Hypertext Links on API root (#1108, #1103)
    Prior to this, accessing the path / would return 404 Not Found. This was changed as follows:

    • / redirects (301 Moved Permanently) to /v1 which is the api base. If the client does not automatcially follow redirects, a json is presented which contains the link to /v1
    • /v1shows a list of main APIs and links to documentation for each resource group. Note this is not a complete list, as the intention is not to list every possible option (We have the swagger document for this). Instead the links work like website links where on the root page you are a presented with a few main cateogories.

    - If the origin optioned is configured in the weavite config, an absolute URI is used. This can be helpful when weaviate is running behind a reverse proxy (which is most likely the case in a production setting). Then weaviate has no way of knowing how the user accesses it without it being explicitly configured. If the origin config is not set, links do not default to the listen/bind address as origin, instead relative links are presented.

    Hypertext Links cross-references (#1106)
    Similar to the API root links, all REST endpoints which can show cross-references now include a read-only field href alongside the existing beacon field. The field contains an HTTP Hypertext Reference to the resprective resources. The same behavior regarding origin in the config and absolute vs relative URIs as outline above applies to these links as well.

    🛠 Fixes

    🛠 Memory leak fixed in contextionary (semi-technologies/contextionary#25)
    We discovered a potential memory leak in a library used in the contextionary. In some cases after long import sessions the contextionary memory usage would keep growing without a limit. We have replaced the code from the external library with custom code in #26 thus fixing the issue.

    🐳 The docker-compose files linked above already reference the new version. If you are running your own setup or the K8s setup via the official helm chart, make sure you reference version <language>0.14.0-v0.4.8 or higher.