Release Notes for DHF 4.1.0

The DHF project now aligns more closely with standard ml-gradle applications.

  • The directory structure and locations of configuration files remain the same as in DHF 4.0.x.

  • See Project Directory Structure for information on the ml-config and hub-internal-config directories.

  • See Gradle tasks for information about ml-gradle tasks specific to DHF.

  • Java deployment commands specific to the data hub were changed as follows:

    • Added:
      • DeployHubOtherServersCommand.java
      • HubDeployDatabaseCommandFactory.java
      • LoadHubSchemasCommand.java
    • Renamed:
      • from LoadUserStagingModulesCommand.java to LoadUserModulesCommand.java
    • Removed:
      • DeployHubDatabasesCommand.java
      • DeployHubFinalSchemasDatabaseCommand.java
      • DeployHubFinalTriggersDatabaseCommand.java
      • DeployHubOtherDatabasesCommand.java
      • DeployHubRolesCommand.java
      • DeployHubSchemasDatabaseCommand.java
      • DeployHubServersCommand.java
      • DeployHubStagingSchemasDatabaseCommand.java
      • DeployHubStagingTriggersDatabaseCommand.java
      • DeployHubTriggersDatabaseCommand.java
      • DeployHubUsersCommand.java
      • DeployUserRolesCommand.java
      • DeployUserServersCommand.java
      • DeployUserUsersCommand.java

  • Custom triggers must now be added to ml-config/databases/(database name)/triggers. (In previous releases, triggers were added to hub-internal-config/triggers or ml-config/triggers.) See ml-grade Project Layout for more information on triggers.

DHF Java API changed to allow DHF to use the Spring Framework.
  • The Java HubConfig class now has a singleton scope.
  • See DHF Java Library for more information.

See Also