Transfer-service - Mappingsets of PIT with no release time
When a new PIT is created, and no release time is given by the user, the transfer-service sets the end time of the corresponding mapping set to sql datetime max.
In the implementation of the PIT feature on the NSIWS 8.1.0, the way the PIT version is identified is as the following:
- identify the PIT mapping set
- Get the current one
- If it's null: it can happen, that only a PIT version exists - use DateTime.Max instead of current time
- If not null: get the mapping set right after the current one - use its ValidTo + 1 sec
This last point "use its ValidTo + 1 sec" fails when the end time of the PIT mappingset is max datetime, because of trying to add the extra second to identify the PIT version.
This ticket should provide a quick fix in the transfer-service, by setting the "valid to" value of the mapping set to max date - 1 sec, for the usecase when no PIT release is provided.