-
Notifications
You must be signed in to change notification settings - Fork 8
Release Notes
Roelant Vos edited this page Jul 7, 2018
·
7 revisions
- Created separate configuration screen, with supporting classes in the base form to get/set changes in configuration variables
- Created separation, and storage of, output and configuration paths to allow different configurations to be saved in separate locations
- Created support for JSON for saving, opening and editing Table Mapping and Attribute Mapping metadata. Note that a SQL Server back-end is still required for activation.
Note - the recent version v1.4 has some underlying repository changes;
- Addition of HUB_ORDER and HUB_TARGET_NAME_IN_LINK in MD_HUB_LINK_XREF
- Addition of BUSINESS_KEY_DEFINITION in MD_STG_LINK_XREF
- New view definition for INTERFACE_HUB_LINK_XREF
If possible, please re-generate the repository to get the latest version (menu -> repository)
Changes in MD model (Metadata Model / TEAM) - 2018-01-03
- Summary: major update to MD model to incorporate various generation changes to fully separate DIRECT and TEAM)
- Intent: making sure all generation metadata is made available in MD / TEAM and all process control and execution metadata is captured in DIRECT. Everything now in sync across the board.
- Changes:
- Renamed MD_SOURCE_CDC_TYPE_XREF to MD_STG_CDC_TYPE_XREF
- Added GENERATE_INDICATOR to MD_STG_CDC_TYPE_XREF. This is to be used to exclude certain ETLs from being generated.
- Added CHANGE_DATETIME_DEFINITION to MD_STG_CDC_TYPE_XREF. This is to pre-calculate business effective dates, if required.
- Updated INTERFACE_VIEW
- Added MD_SOURCE_SYSTEM
- Added MD_SOURCE_DATASET
- Updated MD_SOURCE_STG_XREF to have a FK to SOURCE_DATASET_ID
- Added GENERATE_INDICATOR TO MD_TABLE_MAPPING. This is to exclude certain ETLs from being generated.