Modeling Pitfall #1

[dbera]

The suppression feature (suppress output variables of tasks/fields of record type) is particularly important to link data correctly between compose and run steps. If not done properly especially if a compose step is doing a persistent read from various data stores (where data is being produced by another run step or another compose step), leads to extra data in output of compose steps. As a consequence unwanted chaining of compose and run steps will occur leading to ambiguous multiple "consumes-from-step", breaking the transformation chain. So it is necessary to take into account "suppress" variables to do the linking properly in the generated abstract tspec.