Fusion Server 4.1.1 Release Notes

Release date: 7 November 2018

Component versions:

  • Solr 7.4.0

  • ZooKeeper 3.4.13

  • Spark 2.3.1

  • Jetty 9.3.25.v20180904

  • Ignite 2.3.0

Note
As of Fusion 4.1.1, the SSL configuration procedure has changed. See SSL security for Unix and SSL security for Windows for updated instructions.

New features

Improvements

  • Jetty has been upgraded from version 9.3.8.v20160314 to 9.3.25.v20180904.

  • Two new blob types were added, to support the Managed Javascript index stage and query stage:

    • file:js-index

    • file:js-query

  • Web connector improvements:

    • The connector can now send custom headers with a new addedHeaders property.

    • When the Web connector crawls a Web site and Server Name Indication (SNI) is enabled but the Web site doesn’t support it, you may receive an unrecognized name error. A new property, useIpAddressForSslConnections configures the connector to use the IP address instead of the hostname.

    • Kerberos is now supported with these new properties:

      • kerberosEnabled - Boolean; default false. If true, the connector attempts to perform Kerberos/Spnego authentication when a Web request returns a 401 WWW-Negotiate challenge. If false, the Web connector refuses to attempt Kerberos/Spnego authentication.

      • kerberosPrincipalName - Optional - Use this principal name as the logged-in Kerberos user instead of the environment’s default. If set, you must also specify a keytab with one either kerberosKeytabFilePath or kerberosKeytabBase64 (see below).

      • kerberosKeytabFile - Optional - The path to the Kerberos keytab file that contains the credentials.

      • kerberosKeytabBase64 - Optional - A base64-encoded Kerberos keytab file that contains the credentials.

      See the main topic for additional configuration details.

  • The JDBC Connector has a new convert_type parameter for binary streaming data from a SQL Server

    By default, a JDBC column will automatically use the Solr field type that matches the underlying database’s type of the column. If checked, this will use the field name of the column to choose the Solr field type.

  • The Slack connector can now filter by channel names using a new channel_filters property.

  • When you import objects using the Objects API, a new context parameter specifies the name of an existing app which will be the new context for the imported objects. To support this, the Links API has two new linkType values:

    • inContextOf

    • hasContext

  • Performance improvements in proxy.

    The proxy service now reuses HTTP client instances for better throughput. Customers with high QPS expectations (~ 1000 QPS) are strongly encouraged to upgrade to 4.1.1.

Other changes

  • The Fusion SQL Service (bin/sql) has been added to the default group in conf/fusion.properties. If you do not intend to run the SQL service for self-service analytics, you can remove it from the default group. See Fusion SQL service for more information on using the SQL service.

  • When exporting and importing objects with secret keys, the format is now secret.{object_type}.{object_id}.{number}.password. In the case of data source objects, the format is now secret.{object_type}.{object_id}.{datasource_type}.{number}.password.

  • JavaScript is now thread-safe in pipeline stages.

    This resolves an issue in previous releases where variables in Javascript stages that were not declared with var were shared between threads and other stages using variables with the same name.

  • Headers missing from request.headers in the trusted-http security realm are available again. This includes:

    • fusion-user-realm-name

    • fusion-user-realm-type

    • fusion-user-name

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

Known issues

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