You need to sign in or sign up before continuing.
Introduce Temporal Tables to support includeHistory and As Of features - Data
Introduce the use of SQL Temporal Tables feature, to the .stat suite data DB, to support the Time-machine features 'asOf' and 'includeHistory'.
- The complete Functional specifications are described in this epic.
- The scope of this ticket is for bot features 'asOf' and 'includeHistory'.
- The scope of this ticket is related only to the functionality related to data storage (measures and attributes).
- The implementation for Referential metadata is done in this related ticket.
Tasks
-
New config setting ‘KeepHistory’ to indicate if the history should be kept for the dataspace. -
Make all the changes required during the import/transfer/init to keep historycal changes when the dataspace is configured in this way. - During the merge step, including the insertion to the deleted table, make sure that the update happens within the single transaction so the versions in the history tables are the same for all tables.
-
Introduce temporal tables for all the tables storing data. -
Document the data database structural changes.
-
-
Modify the creation of mappingsets to include the new parameters to query ‘FOR SYSTEM_TIME CONTAINED IN|AS OF|ALL‘ -
Create new views/queries that include as of/contain in expressions -
Return a not-supported error in the following cases: - When the user tries to create a PIT version while the setting ‘KeepHistory’ is set to true for a given dataspace.
- When the user imports/transfers data or inits a dataflow, for which the DSD is non final or has non-backward compatible changes, while the setting ‘KeepHistory’ is set to true for a given dataspace. (nothing to change for this in this ticket)
-
Temporarly configure qa:reset to keep history
Edited by jean-baptiste nonin