Release Notes

The Semantic Search release notes provide information about the features and improvements in each release, as well as various bug fixes. The Semantic Search versioning scheme is based on semantic versioning. The full version is composed of three components:

major.minor.patch

e.g., 1.2.3 where the major version is 1, the minor version is 2, and the patch version is 3.

Note

Releases with the same major and minor versions do not contain any new features. Releases with different patch versions contain fixes for bugs discovered since the previous minor. New or significantly changed features are released with a higher major or minor version.

Semantic Search 3.8.0

Released: 1 March 2022

Important

Semantic Search 3.8.0:

  • Deployment and Operations Improvements – Key components updated to newer versions
  • Semantic Search – New and improved connector management

Note

Semantic Search version 3.8.0 requires:
  • Semantic Objects version 3.6.0 or 3.7.0 with disabled connector management, or version 3.8.0 or later
  • Workbench version 3.8.0 or later
  • GraphDB version 9.10.1 or later, as well as the required version of Elasticsearch corresponding to the used GraphDB Elasticsearch connector version.

You can find a list with all external dependencies here.

New Features

  • Semantic Search
    • New and improved connector management:
      • Connector management has been moved from Semantic Objects to Semantic Search.
      • Connectors and indexes are only recreated and re-indexed on changes in the connectors model.
      • Connectors and indexes are created asynchronously from schema bind operation. To manually check the currently running tasks, see the SOML status.
      • Better connector creation monitoring in the Workbench

Improvements

  • Deployment and Operations Improvements
    • Upgraded to Semantic Objects 3.8.0
    • Upgraded to GraphDB 9.10.3
    • Updated to Kong Helm chart 2.5 (Kong 2.6)
    • Updated Spring Boot to 2.5.9

Bug Fixes

  • PLATFORM-3932 Semantic Search should not trigger schema migration