Fusion Server 4.1.0 Release Notes

Release date: 17 July 2018

Component versions:

  • Solr 7.4.0

  • ZooKeeper 3.4.11

  • Spark 2.3.1

  • Jetty 9.3.8.v20160314

  • Ignite 2.3.0

New features

  • App Studio integration

    Fusion App Studio is now integrated into the Fusion Server UI for seamless search UI development. You can open App Studio from the Fusion workspace by navigating to App Studio > Build new UI.

    Integrated App Studio

Improvements

  • Connector improvements

    • The Confluence connector now indexes labels for spaces and pages.

    • The Web connector can be configured to deduplicate pages whose content is identical.

    • The Slack connector is no longer deprecated.

  • UI improvements

    • The Object Explorer now supports filtering by object type.

    • Objects in the UI now include an "Explore" button that opens the Object Explorer view for that object.

    • UI panels can now be resized horizontally.

    • Text input areas can now be opened as pop-out modals for easier editing.

  • Connectors SDK

  • Import/export improvements

    • Additional parameter substitutions are now supported on object import.

Other changes

  • Better heuristics for the splits_per_shard field in the Catalog API.

  • Fusion’s SparkSQL engine is no longer a beta release.

  • Ports are now preconfigured for Spark multinode communication, using these parameters in the Configurations API:

    • spark.driver.port

    • spark.executor.port

    • spark.blockManager.port

    • spark.fileserver.port

  • A request ID can now be defined in order to add context to logs.

  • The Jobs API now provides better performance.

  • The system collections named audit_logs and logs have been replaced and extended with a new system collection, system_logs.

Known issues

  • Some headers are missing from request.headers in the trusted-http security realm, including the following:

    • fusion-user-realm-name

    • fusion-user-realm-type

    • fusion-user-name

    • fusion-user-permissions lacks the role restriction assigned with the security realm.

  • The Tika parser and Tika stage Return parsed content as XML option works only if the input document is also HTML/XML.