v4.1.0
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-user-configandhub-internal-configdirectories. -
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.javaHubDeployDatabaseCommandFactory.javaLoadHubSchemasCommand.java
-
Renamed:
- from
LoadUserStagingModulesCommand.javatoLoadUserModulesCommand.java
- from
-
Removed:
DeployHubDatabasesCommand.javaDeployHubFinalSchemasDatabaseCommand.javaDeployHubFinalTriggersDatabaseCommand.javaDeployHubOtherDatabasesCommand.javaDeployHubRolesCommand.javaDeployHubSchemasDatabaseCommand.javaDeployHubServersCommand.javaDeployHubStagingSchemasDatabaseCommand.javaDeployHubStagingTriggersDatabaseCommand.javaDeployHubTriggersDatabaseCommand.javaDeployHubUsersCommand.javaDeployUserRolesCommand.javaDeployUserServersCommand.javaDeployUserUsersCommand.java
-
-
Custom triggers must now be added to
ml-config/databases/databasename/triggers. (In previous releases, triggers were added tohub-internal-config/triggersorml-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
HubConfigclass now has a singleton scope. - See DHF Java Library for more information.
For more information on the bug fixes in this release, see the change log.