MarkLogic Data Hub 5.2 - Release Notes

Data Hub 5.2.1

Important: Upgrading to this release from earlier than 5.2.0 would trigger a reindexing of the STAGING and FINAL databases.

Bug fixes.

Data Hub 5.2.0

Data Hub 5.2.0 includes the following new features and changes:

Important: Upgrading to this release from earlier than 5.2.0 would trigger a reindexing of the STAGING and FINAL databases. See details.

Performance

New Index to Improve Mastering Performance

This release adds a new index to the STAGING and FINAL databases to improve mastering performance. These databases will be reindexed when you deploy your application for the first time after upgrading. During reindexing, some services are not available, including search and mastering.

The size of the data in these databases determines the duration of the reindexing. See How reindexing works, and its impact on performance.

Security

New Security Roles
New security roles are introduced for more granular permission management and for easier migration from an on-premise installation to DHS:
  • data-hub-operator
  • data-hub-developer
  • data-hub-admin
  • data-hub-security-admin
  • data-hub-monitor

The old security roles are still valid; however, the new roles are preferable.

Requires MarkLogic Server 10.0-3.

See Users and Roles.

Tools

New Java Method to Run Flows Without Local Project Files

The FlowRunner class of the Data Hub Java API now includes a new runFlow method which does not require project files in the local filesystem. This method accepts a single parameter of type FlowInputs and is the preferred method for running flows programmatically.

Older runFlow methods are retained for backward compatibility only.

See Run a Flow Using the Data Hub Java API.

New Executable Client JAR for Running Flows

A new client JAR for running flows is now available. This method of running flows depends only on a JVM and doesn't require project files or Gradle.

See Run a Flow Using the Data Hub Client JAR

Release Notes for Earlier Versions