New Direct Access gateway version (1.7.13)

Direct Access gateway 1.7.13 introduces both new and enhanced features, and resolves several issues. For upgrade instructions and a list of resolved issues, see Upgrading the Direct Access gateway installation

This version introduces new and enhanced functionality as well as several bug fixes.

• Extended authentication support

  The following connectors now support Single Sign-On (Kerberos) authentication:

  • Apache Hive
  • Cloudera Impala
  • Teradata

  • Microsoft SQL Server

  In addition, the Teradata connector now supports LDAP authentication.

• Improved handling of File connector reloads

  The Analytics engine would sometimes cache connections from earlier sessions and send a request to a pod that had been requested to shutdown. This would cause reloads to fail with the following error:

  Connector error: data loading error (DirectAccess-4008)

  From this version, reload requests to a pod that is no longer active will be rejected and routed to an available pod.

• Improved reload measurement logging

  Reload measurement logging has been improved. This will allow both customers and Qlik Support to gain further insights into reload performance. As part of the improvements, the logging level will now be INFO and the log message has been adapted for use with the Direct Access gateway monitoring tool. Additionally, the following information will now be shown in the log:

  • Percentage of the reload time spent on Web Socket transfer.
  • A rough estimation of the throughput between the data source and Direct Access gateway.
  • A rough estimation of the throughput between the Direct Access gateway and Qlik Cloud.

• Ability to set how many rows to fetch per bulk when using the ODBC (via Direct Access gateway) connector

  A new Number of rows to fetch per bulk option has been added to the ODBC (via Direct Access gateway) connector. While the default value is optimal for most scenarios, if you encounter significant performance issues, adjusting this value might help.

• Row count validation during reloads

  The row count from all non-File Direct Access gateway connectors (the number of rows it reads) will now be validated to ensure that it matches the number of rows sent to the engine. If a mismatch is detected, the reload will fail with an appropriate error, thereby preventing inconsistent data loading.

• Improved error handling of async commands

  Identification and handling of response errors resulting from failed async commands has been improved. This enhancement will facilitate better troubleshooting of async command failure.