Product Selector

Fusion 5.9
    Fusion 5.9

    Fusion Server 4.2.6 Release Notes

    Table of Contents

    Release date: 31 March 2020

    Component versions:

    Solr 7.7.2

    ZooKeeper 3.4.13

    Spark 2.3.2

    Jetty 9.4.19.v20190610

    Ignite 2.6.0

    More information about support dates can be found at Lucidworks Fusion Product Lifecycle.

    New features

    • Support is added for individually selecting rules to publish in the Fusion UI:

      Individually publish rules in the Fusion UI

    Improvements

    • The GitHub connector no longer accepts username and password as authentication methods. Instead, GitHub oAuth token Authentication is used to perform GitHub requests. See the GitHub oAuth authentication page for more information.

    • The Jira connector is updated to use the latest available authentication methods.

    • The Google Drive connector allows debug logging to view HTTP traffic securely.

    • The Blob Store gives a more informative error message when an uploaded file has invalid schema or fields.

    • Various UI improvements.

    Bug fixes

    • Fixed a bug that lowered performance on large query plans.

    • Fixed a bug with the Alfresco connector that caused old and new versions of a document to be indexed during a recrawl. Now, only the latest document is indexed.

    • Fixed a bug with the Alfresco connector that caused a moved document to be indexed at the previous and current location. Now, only the document in the current location is indexed.

    • Fixed a bug with the Alfresco connector that prevented the acls_ss field from updating unless Force Recrawl was selected.

    • Fixed a bug with the FTP connector that sometimes prevented files with non-English filenames from being indexed.

    • Fixed a bug with the Scala script job that sometimes resulted in job failures when indentation was used.

    • Fixed a bug with V2 connectors that sometimes resulted in jobs completing before all documents were indexed.

    • Fixed a bug with V2 connectors that sometimes caused crawls to stall and fail due to an Out of Memory (OOM) error.