Release Notes¶

Improvements¶

Search Service now supports Elasticsearch with enabled security using basic authentication and servers using non public SSL certificate authorities. We have deprecated the use to Spring Elasticsearch configurations (spring.elasticsearch.*) and they have been replaced by the set of configurations described in the Elasticsearch Configurations. Here is a short list of the old configurations and their replacement

• spring.elasticsearch.uris and spring.elasticsearch.rest.uris are replaced by elasticsearch.host
• spring.elasticsearch.username and spring.elasticsearch.rest.username are replaced by elasticsearch.username
• spring.elasticsearch.password and spring.elasticsearch.rest.password are replaced by elasticsearch.password
• spring.elasticsearch.connectionTimeout, spring.elasticsearch.connection-timeout, spring.elasticsearch.rest.connectionTimeout and spring.elasticsearch.rest.connection-timeout are replaced by elasticsearch.connectionTimeout
• spring.elasticsearch.socketTimeout, spring.elasticsearch.socket-timeout, spring.elasticsearch.rest.readTimeout and spring.elasticsearch.rest.read-timeout are replaced by elasticsearch.socketTimeout
• spring.elasticsearch.pathPrefix and spring.elasticsearch.path-prefix are replaced by elasticsearch.pathPrefix

The use of the old configurations are still permitted but they will issue a warning in the logs. The support for these configurations will be removed in future versions.

Improvements¶

Search Service now is compatible with the GraphDB 10.4. The change also removes the support for earlier versions of GraphDB due to incompatible connector configurations. If you need to use GraphDB version 10.2.x you need Search Service 4.0.1.

• Updated Elasticsearch dependencies to 7.17.15

Improvements¶

Search Service now supports Elasticsearch with enabled security using basic authentication and servers using non public SSL certificate authorities. We have deprecated the use to Spring Elasticsearch configurations (spring.elasticsearch.*) and they have been replaced by the set of configurations described in the Elasticsearch Configurations. Here is a short list of the old configurations and their replacement

• spring.elasticsearch.uris and spring.elasticsearch.rest.uris are replaced by elasticsearch.host
• spring.elasticsearch.username and spring.elasticsearch.rest.username are replaced by elasticsearch.username
• spring.elasticsearch.password and spring.elasticsearch.rest.password are replaced by elasticsearch.password
• spring.elasticsearch.connectionTimeout, spring.elasticsearch.connection-timeout, spring.elasticsearch.rest.connectionTimeout and spring.elasticsearch.rest.connection-timeout are replaced by elasticsearch.connectionTimeout
• spring.elasticsearch.socketTimeout, spring.elasticsearch.socket-timeout, spring.elasticsearch.rest.readTimeout and spring.elasticsearch.rest.read-timeout are replaced by elasticsearch.socketTimeout
• spring.elasticsearch.pathPrefix and spring.elasticsearch.path-prefix are replaced by elasticsearch.pathPrefix

The use of the old configurations are still permitted but they will issue a warning in the logs. The support for these configurations will be removed in future versions.

Bug Fixes¶

• Fixed an issue that was preventing JWT tokens, with a single role as string, to be accepted by the service.
• Fix an issue with GraphDB connection management that could cause locking of the service.

Improvements¶

• Upgraded to Semantic Objects 4.1.0
• Updated Spring Boot to 2.7.17
• Updated Spring Security to 5.7.11
• Updated Elasticsearch dependencies to 7.17.14
• Updated Tomcat to 9.0.82
• Updated SnakeYaml to 2.2

New Features¶

New and improved connector management:

• Connector management has been updated to work with the latest version of GraphDB.

Improvements¶

• The minimal version of the Java runtime has been updated to be Java 11
• Upgraded to Semantic Objects 4.0.3
• Upgraded to GraphDB 10.2.5
• Updated Spring Boot to 2.7.15
• Updated Elasticsearch dependencies to 7.17.12
• Updated to GraphQL Java 20.4
• Breaking change: Json Web Token (JWT) library brings in more stringent handling of secret keys used for decrypting token information. The previous implementation lacked sufficient enforcement of keys for the decryption algorithms. For additional details about the minimum key lengths, please refer to the Signature Algorithms Keys section on the Java JWT library page.

Migration¶

To migrate to Semantic Search 4 you can follow the next steps:

• Unbind the SOML schema from the Semantic Search. This will cause the old connectors to be removed along with the Elasticsearch indexes. This could be done by evaluating curl -X DELETE --url http://<semantic-search:port>/soml/<schemaId>/search
• Upgrade your GraphDB 9 installation to GraphDB 10 using the GraphDB migration guide.
• Optionally you can upgrade your Elasticsearch version to the latest supported for GraphDB 10.2.x this is Elasticsearch 7.x.
• Bind the SOML schema to the Search Service. This could be done by evaluating curl -X PUT --url http://<semantic-search:port>/soml/<schemaId>/search
• Wait for the data to be indexed

New Features¶

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¶

• 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