Convert Your Artifacts from Quickstart to Hub Central
The format of entity models, flows, and steps required by Hub Central is different from the format required by QuickStart.
- In Hub Central, entity models allow properties of entity types to be used as facets when filtering your data.
- In QuickStart, you run a flow with steps in it, and the steps are embedded in the flow configuration. In Hub Central, you run individual steps, and each step is in its own file, which the flow configuration refers to.
If you have existing Data Hub 5.0–5.2 models, flows, and steps that you intend to use in Hub Central in DHS/an on-premises or local environment, you must convert them to the Hub Central format. After the conversion, QuickStart will no longer recognize those files. If you do not plan to use Hub Central, the conversion is not required.
As of Data Hub 5.4, a new set of match/merge formats have been created which opens up new capabilities and eliminates redundant configuration that is completed by Modeling with Entity Services. This new set of match/merge formats must be associated with an Entity Type and are required for compatibility with the Hub Central User Interface, but will not be compatible with Data Hub QuickStart.
- Migrating 4x Flows.
- Add them to new 5.x or 6.x flows.
The Data Hub Gradle Plugin and the Data Hub Client JAR can handle both formats.
Before you begin
You need:
- Java JRE (OpenJDK) 8
- MarkLogic Server (See Version Compatibility.)
- Gradle 6.4 up to the latest 7.x release
Procedure
- In the QuickStart format, mapping properties are stored in mapping configuration files, separate from the mapping step.
- In the Hub Central format, all mapping properties are included in the mapping step.
After running hubConvertForHubCentral, the old mapping configuration files might still exist in other environments.