Extend the PITInfo method to allow changing the PITReleaseDate
As Bo Marleau,
I want a transfer feature to easily change a Pit datetime (without requiring to upload data) if there is already an embargo waiting,
So that I do not need to upload data anymore when just needing to change the PIT datetime.
Functional specifications
Extend the current /pointintime/PITInfo
method by adding an optional "PITReleaseDate" parameter. When this parameter is provided (filled or empty), in addition to getting the latest PiT info, the method would set the new date (to the date provided or infinity).
If the provided PITReleaseDate refers to a date and time in the past, then, similarly to the current behavior for the /import
transfer method, the PIT release is accepted and immediately activated and released right at the end of the transaction (see reference documentation).
query example:
POST /pointintime/PITInfo
{
"dataspace": "design",
"dataflow": "OECD:DF_MEI(1.0)",
"PITReleaseDate": "2022-09-08T00:00:00+02:00"
}
Response example:
{
"PITVersion": "A",
"PITReleaseDate": "2022-09-07T22:00:00+00:00",
"PITRestorationDate": null
}
Specific new message
When the user submit an update of the PITReleaseDate in the past, the response form the transfer service should be a 200
successfully message with the following notification: The PITReleaseDate update has successfully occurred in the past. As a consequence, the Point-in-time data version for the data structure {0} has automatically been released.
Extra FE implementation
Once this ticket is implemented, the DLM needs to be enhanced to allow using this feature. See: dotstatsuite-data-lifecycle-manager#297