Author: npeltier
Date: Mon Sep 4 19:48:33 2017
New Revision: 1807296
URL: http://svn.apache.org/viewvc?rev=1807296&view=rev
Log:
[sling pipes] update curl & status documentation
Modified:
sling/site/trunk/content/documentation/bundles/sling-pipes.mdtext
Modified: sling/site/trunk/content/documentation/bundles/sling-pipes.mdtext
URL:
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/sling-pipes.mdtext?rev=1807296&r1=1807295&r2=1807296&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/sling-pipes.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/sling-pipes.mdtext Mon Sep
4 19:48:33 2017
@@ -98,7 +98,7 @@ which will return you the path of the re
In the eventuality of a long execution (synchronous or asynchronous), you can
retrieve the status of a pipe, by executing
- GET /etc/pipes/mySamplePipe**.status**.json
+ GET /etc/pipes/mySamplePipe.status.json
##### Request Parameter `binding`
@@ -136,6 +136,7 @@ default response is truncated to 10 item
##### Request Parameter `async`
allow asynchronous execution of the given type. This is advised in case you
plan your pipe execution to last longer than the session of your HTTP client.
If used, the returned value will be id of the created sling Job.
+In that case you can monitor the pipes path with `status` selector as
described above until it has the value `finished`.
## Registered Pipes
@@ -217,7 +218,7 @@ as an example,
will either return `/content/foo` either nothing depending on it
not containing `@foo=bar`
- echo('content/foo').name('FOO').grep('slingPipesFilter_test','${FOO.foo ==
"bar"}'
+ echo('content/foo').name('FOO').grep('slingPipesFilter_test','${FOO.foo ==
"bar"}').run()
is an equivalent
