In the Trigger Task; there is an Option Do not start a new execution if one is already active
In the Documentation this option Do not start a new execution if one is already active allows you prevent a Pipeline from running again if a previous execution of that Pipeline is already running.
Does this option ignore the second request if it is sent at the same time or does it queue it up?
HI SpiroTaleski
Can you suggest any snap through which i can achieve this. It is a dynamic pipeline which would iterate for all the tables in schema so i won't be able to hardcode column names at runtime
Then the better option is to have one configuration file(expression library) where the column types conversions will happen(along with my suggestion from above). Then from SnapLogic pipeline you will call the configuration file and pass the source columns that should be converted.
