A concept and syntax to provide a universal data format, for storing all essential informations, that are needed to implement or generate a data loading process for a data vault model.
It should be optional possible to declare all key and content columns on table level.
This will enforce consistency of table structures and hash value composition between multiple pipelines by copying the declaration between dvpds or by "including" Snippets during preprocessing.
All hash key relevant properties will also be part of this declaration.
Field mappings can be reduced to the declaration of table name, (in case of other name) column name and all relation specific annotations. In case of type conversions, the target type must be also declared in the field mapping to prevent accidental type mismatches.
Hash declarations on field mapping level will be ignored. This will result in a compiler warning.
The use of declaration of columns can be decided individually. Compiler options or model profile options might enforce this for specific stereotypes.
It should be optional possible to declare all key and content columns on table level.
This will enforce consistency of table structures and hash value composition between multiple pipelines by copying the declaration between dvpds or by "including" Snippets during preprocessing.
All hash key relevant properties will also be part of this declaration.
Field mappings can be reduced to the declaration of table name, (in case of other name) column name and all relation specific annotations. In case of type conversions, the target type must be also declared in the field mapping to prevent accidental type mismatches.
Hash declarations on field mapping level will be ignored. This will result in a compiler warning.
The use of declaration of columns can be decided individually. Compiler options or model profile options might enforce this for specific stereotypes.