Release NotesFusion Connectors
Fusion Connectors are continuously improving with new features, updated functionality, performance upgrades, and bug fixes. This article summarizes these changes.
|Starting in January, 2023, Fusion Connector releases are documented separately from Fusion releases. Release details prior to that date are found in the Fusion release notes.|
The SharePoint Optimized V2 connector is updated to v2.0.0.
|SharePoint Optimized V2 v2.0.0 is compatible with Fusion 5.9.1 and later. See the configuration reference page for the latest version and compatibility details.|
The connector supports remote configurations.
The LDAP ACLs V2 connector is updated to v2.0.0.
|LDAP ACLs V2 connector v2.0.0 is compatible with Fusion 5.9.1 and later. See the configuration reference page for the latest version and compatibility details.|
The updated connector:
Supports remote configurations.
Uses the SDK that correctly processes the NOT-EQUAL phrase in delete-by-query.
Supports unauthenticated proxy.
The SharePoint Optimized V2 connector is upgraded to v1.6.0.
|If you are on Fusion 5.9.0 or later, you must use the SharePoint Optimized V2 v1.6.0 connector or later.|
For SharePoint Online connector OAuth authentication and NTLM authentication, an issue with the SharePoint Optimized V2 connector crawl was fixed. Now the crawl fails if the data source is configured with incorrect credentials.
When the moderation status of a published document moves to unpublished, the document is deleted from the index.
The URL that requests folder metadata is now properly encoded and retrieves requested files correctly.
The LDAP ACLs V2 connector is upgraded to v1.5.0.
|If you are on Fusion 5.9.0 or later, you must use the LDAP ACLs V2 connector v1.5.0 or later.|
The datasource indexing job will now return an error when invalid access credentials are provided instead of reporting a success.
Securityparameter is now set to
The Kaltura V2 connector is upgraded to v1.2.0.
Fixed an issue that occurred when reaching Kaltura’s API limit of 10,000 documents. Indexing over 10,000 documents should now work as expected.
The JDBC V2 Connector is upgraded to v2.3.0.
The JDBC V2 connector now supports indexing character large objects (CLOBs).
The Kaltura V2 connector is upgraded to v1.1.0.
NoClassDefFounderror in the connector has been fixed.
The SharePoint Optimized V2 Connector is upgraded to v1.5.0.
MapDB tables that are no longer needed after indexing are now automatically removed when the indexing job completes.
The connector no longer uses the index pipeline client when the
onlyMetadataproperty is set to
trueor when Tika async parsing is enabled. Instead, documents are processed using the Connectors SDK’s
The Web V2 Connector is upgraded to v1.3.0.
A bug with the Rewrite URI configuration option that prevented the configuration from being applied during the indexing job has been fixed.
The SAML, Form, and NTML authorization form fields are updated to match those present in the Web V1 connector.
The JDBC V2 Connector is upgraded to v2.2.0.
A bug that affected JDBC datasources with large document sizes has been fixed. Previously, the indexing job would fail and produce a Solr error message similar to the following:
Document contains at least one immense term in field="FIELD_NAME"
This bug has been fixed and indexing large documents should now work as expected.
The LDAP ACLs V2 Connector is upgraded to v1.4.0.
Added support for the graph security trimming stage for Active Directory in Azure.
A bug that prevented the connector from retrying after a connection error has been fixed.
The JDBC V2 Connector is upgraded to v2.1.0.
statement.setMaxRows()field was added to resolve a timeout error for large queries on a JDBC data source.
The SharePoint Optimized V2 Connector is upgraded to v1.4.0.
A new field,
_lw_document_type_s, has been added to differentiate between document types. SharePoint content documents use the value
contentDocument. ACL documents use the value
A bug that caused a
NullPointerExceptionerror when the
listDefaultDisplayFormUrlvalue is null has been fixed.
A bug that prevented the connector from indexing SharePoint Online URLs containing certain special characters, such as
#, has been fixed.
A bug that stopped the indexing job unexpectedly when the
digestValuerequest fails has been fixed.
The LDAP ACLs connector is upgraded to v1.3.0.
Fixed a memory leak that resulted in an
OutOfMemoryErrorruntime error, causing recrawls to quickly fail.
The SharePoint Optimized V2 Connector is upgraded to v1.3.0.
Fixed an issue where sometimes the connector did not index all attachments in full crawls.
Fixed an error related to OAuth authentication where the body would not return the expected value.
Folders with unique permissions no longer inherit list permissions instead of their own.
The Web V2 Connector is upgraded to v1.2.0.
Fixed a bug that sometimes resulted in an
OutOfMemory: Java Heap Spaceerror when the connector was run remotely.
Fixed a dependency issue that sometimes resulted in a
Error starting controllerserror that caused the job to fail.
The LDAP ACLs V2 Connector is upgraded to v1.2.0.
Fixed a bug that removed access control lists (ACLs) during incremental crawls in Azure Active Directory. This bug resulted from a deviation from the LDAP ACLs V2 connector’s unique incremental crawl behavior for Azure Active Directory.
Fixed a bug that sometimes deleted ACLs that the indexing job failed to update during its previous run.
Known issue: The job may complete with a "Successful" status even when a network communication error occurred.
The SharePoint Optimized V2 Connector is upgraded to v1.2.0.
Fixed a bug that sometimes generated a "User cannot be found" error statement and prevented the connector from indexing files.
Updated the description of the Item size limit property to clarify its behavior.
The Web V2 connector is upgraded to v1.1.0.
Fixed a bug that sometimes prevented the connector from parsing PDF, Word, Excel, and other file types.
Some conflicting dependencies were removed to resolve errors.
A missing dependency, guava-retrying, was added to resolve a
A bug was fixed that resulted in the connector performing full crawls instead of recrawling as expected.
Known issue: The counter values in the Datasources > DATASOURCE_NAME > Job History view do not reflect actual values, when the datasource uses the Web V2 connector.
The Sharepoint Optimized V2 connector is upgraded to v1.1.0. This upgrade includes several bug fixes.
A bug that sometimes prevented files from being deleted as expected when the datasource was recrawled was fixed.
A bug that prevented the connector from indexing data within certain lists was fixed.
When indexing data to the
MetaInfo_sfield, an error could occur that prevented indexing data when the data was too large. Now, data larger than 32,766 bytes is indexed to the
The connector now accepts URLs with spaces.