classic pipeline example: more great parts v_0
authorFrantišek Kučera <franta-hg@frantovo.cz>
Fri, 30 Nov 2018 19:09:08 +0100
branchv_0
changeset 166 d8be473e0d86
parent 165 3074cf4158d2
child 167 0ec0b9d70bef
classic pipeline example: more great parts
relpipe-data/classic-example.xml
--- a/relpipe-data/classic-example.xml	Fri Nov 30 18:45:36 2018 +0100
+++ b/relpipe-data/classic-example.xml	Fri Nov 30 19:09:08 2018 +0100
@@ -65,6 +65,16 @@
 			Thus optimal language can be used for each task.
 		</p>
 		
+		<p>
+			The pipeline is reusable which is a big advantage compared to ad-hoc operations done in CLI or GUI tools.
+			Thus we can feed different data (with same structure of course) into the pipeline and get desired result.
+		</p>
+		
+		<p>
+			Particular steps in the pipeline can be added, removed or exchanged. 
+			And we can also debug the pipeline and check what each step produces (e.g. use <code>tee</code> to duplicate the intermediary outputs to a file or just execute only some first steps of the pipeline).
+		</p>
+		
 		<h2>The pitfalls</h2>
 		
 		<p>