The init/dataflow method of transfer service shouldn't regenerate actual CC of other dataflows
Currently the init/dataflow
method of transfer service regenerates the mapping sets and actual content constraints of all dataflows related to the DSD of the targeted dataflow.
Instead of this behaviour, the init/dataflow
method should only (re)generate the mapping sets and actual CCs of the target dataflow, but not the ones belonging to other dataflows.
An extra improvement should be also adressed in this ticket, since the code is closely related:
-
For data imports and transfers, recreate mappingsets only if there has been structural changes or first time the MSD or DSD are created. -
Update mappingset info (sql query and validity info) only when there has been a PIT release and the functions rollback and restore.
Edited by Pedro Carranza