From af773f3fd0152cb92ea9424d23005550243fce28 Mon Sep 17 00:00:00 2001 From: Andrey Pavlov Date: Fri, 18 Dec 2015 16:41:16 +0300 Subject: [PATCH] Adding doc about data source placeholders Partiallly-implements bp: edp-datasource-placeholders Change-Id: I8d75303d1d3bf1c2d2661769f3b85218f4bd17ac --- doc/source/userdoc/features.rst | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/doc/source/userdoc/features.rst b/doc/source/userdoc/features.rst index 333a0118..4decbe90 100644 --- a/doc/source/userdoc/features.rst +++ b/doc/source/userdoc/features.rst @@ -233,3 +233,20 @@ Public objects created in one tenant can be used from other tenants (for example, a cluster can be created from a public cluster template which is created in another tenant), but modification operations are possible only from the tenant in which object was created. + +Data source placeholders support +-------------------------------- + +Sahara supports special strings that can be used in data source URLs. These +strings will be replaced with appropriate values during job execution which +allows the use of the same data source as an output multiple times. + +There are 2 types of string currently supported: + +* ``%JOB_EXEC_ID%`` - this string will be replaced with the job execution ID. +* ``%RANDSTR(len)%`` - this string will be replaced with random string of + lowercase letters of length ``len``. + +After placeholders are replaced, the real URLs are stored in the +``data_source_urls`` field of the job execution object. This is used later to +find objects created by a particular job run.