Weaviate v0.22.13 Release Notes

Release Date: 2020-07-10 // almost 2 years ago
  • ๐Ÿณ Docker image/tag: semitechnologies/weaviate:0.22.13
    ๐Ÿ‘€ See also: example docker compose files in English, German, Dutch, Italian and Czech.

    ๐Ÿ’ฅ Breaking Changes

    ๐Ÿ†• New Features

    โž• Add _semanticPath underscore prop to Get{} queries with explore set (#1168)
    The semantic path is the path between a search term and each result. For example if the search term is iphone and the first result is an article about "Microsoft Inc.", then the path would be how to get from the search term to the result, for example ["iphone", "apple", "company", "microsoft"]

    ๐Ÿ— The semantic path can be queried using the _semanticPath GraphQL property alongside the schema-defined properties in GraphQL. Building a semantic path is only possible if an explore: {} parameter is set. As the explore term represents the beginning of the path and each search result represents the end of the path. If no explore: {} parameter is set, the query is just a list query and not a search query, therefore no path can be built. Since explore:{} queries are currently exclusively possible in GraphQL, the _semanticPath is therefore not available in the REST API, either.


    1. Due to the relatively high cost of the underlying algorithm, we recommend to limit requests including a _featureProjection in high-load situations where response time matters. Avoid parallel requests including a _featureProjection, so that some threads stay available to serve other, time-critical requests. The maximum supported request limit (to be set through the limit: <int> parameter is 25
    2. The semantic path feature requires a contextionary version of at least ...-v0.4.14 which is used in the provided docker-compose files linked above.

    ๐Ÿ›  Fixes