In the editor header, a series of buttons allows to manage pipeline execution.
Here are the respective buttons functions:
Run without cache: runs the whole pipeline up to the runToFinishLine action
Run with cache: runs the pipeline, but uses the cache files (created with runTo), to speed up development/debugging
Stop: stops current execution/preview process
Clean: delete all cache filesIn the editor, this toolbar is accessible by clicking on an action output pin.
This toolbar offers the following buttons:
fast preview: view the 100 first lines at pin
RunTo: run to the pin and create a cache file
Clean: delete cache file at this pinMost of the time, a fast preview is sufficient to verify whether the action parameters are correct.
This is the fastest method and is therefore recommended to inspect output data.
For convenience, a double-click on a pin performs a preview.
If the action generates an image rather than a table, the 100-line limit is ignored and the entire data is processed at the pin.
If you need to debug specific line(s) beyond the first 100 rows, follow this process:
Creating a cache file with RunTo, once the action parameters are set, also enables much faster previews for downstream actions in the pipeline.
Whenever possible, ETL will reuse the cache file instead of recomputing everything from scratch.
You can persist cache files between work sessions by enabling the related checkbox in the global pipeline parameters.
When user starts the pipeline execution, the process panel pops and displays the execution log in its first tab.
The index(es) of the action(s) where the error(s) occurred are shown in the log,
and an icon is displayed on the corresponding action(s) in the pipeline.
You can click on the action index in the log window to automatically center the view on the affected action.
User can stop the execution of the pipeline at any time. Click on the square icon on the right of the toolbar (
) to stop the execution of the current pipeline.
After a successful preview execution at a pin or a full execution, results are available in the Data and Records tabs.
Data tab display a table of the data as it is at the output pin where you requested a preview (by double-click on the pin). No data is available here if the action generates an image. This is very helpful to debug the action parameters you set.
Records tab display the list of records and images generated by the pipeline if any.
For more inormation see Bottom-right panel - Process