Release notes v3.1.0.0

April 2024 - Connectivity Hub v. 3.1.0.0

The following features and updates are new in this release of Connectivity Hub.

System enhancements

Feature	Description
Vector search compatibility	Vector Search for Microsoft Azure Search is now supported in this release of Connectivity Hub. You can use vector search to transform your content into numeric representations, enabling you to retrieve the content that is most related to your search query, without requiring the terms in the query to be exact matches to your indexed content. For more information, see How to configure your Azure Search target.
SQLClient default encryption	Due to a vulnerability fix on the SQL Client, the default encryption flag for SQL connections and Connectivity Hub database connections has been set to True. If you do not support encryption in your database connections, you must use an advanced connection configuration and override the default encryption flag by specifying Encrypt=false in the connection string. For more information, see How to Install and Configure Connectivity Hub. If you are upgrading your instance of Connectivity Hub and you do not use encryption for your databases, you will need to reconfigure all of your databases to specify Encrypt=false. For more information

Feature

Description

Vector search compatibility

Vector Search for Microsoft Azure Search is now supported in this release of Connectivity Hub. You can use vector search to transform your content into numeric representations, enabling you to retrieve the content that is most related to your search query, without requiring the terms in the query to be exact matches to your indexed content. For more information, see How to configure your Azure Search target.

SQLClient default encryption

Due to a vulnerability fix on the SQL Client, the default encryption flag for SQL connections and Connectivity Hub database connections has been set to True. If you do not support encryption in your database connections, you must use an advanced connection configuration and override the default encryption flag by specifying Encrypt=false in the connection string. For more information, see How to Install and Configure Connectivity Hub.

If you are upgrading your instance of Connectivity Hub and you do not use encryption for your databases, you will need to reconfigure all of your databases to specify Encrypt=false. For more information

Fixed Issues

If folder enumeration failed at a specific page in a previous crawl, the next full crawl would continue from that page and would not enumerate the previous pages. Connectivity Hub assumed that the non-enumerated pages were removed and did not include them in the index.
If you started a crawl on an multi-server environment, the UI would display the crawl as Cleaning or Completed despite the crawl still running in the background.
If you were using an Azure Active Directory target, Connectivity Hub experienced delayed responses when fetching the user security group membership due to Azure Active Directory initialization.
Changes to the timeout value for Elastic targets were not picked up due to caching issues.
The value for _ExecutionContext was "AccessPoint" for both Connectivity Hub Testbench and target crawls. _ExecutionContext now uses the value "TestBench" for Testbench and "Target" for target crawls.
Metadata with the Searchable property was not imported to Microsoft Azure.
If you ran a full update of an Amazon S3 connector with a Microsoft Search target, the update would fail due to extra validation that was implemented to prevent incorrectly configured metadata.