ETL scenario language - Revision history

Maxlmus at 03:59, 14 August 2014

2014-08-14T03:59:43Z

Maxlmus at 17:11, 5 August 2014

2014-08-05T17:11:56Z

Maxlmus at 17:11, 5 August 2014

2014-08-05T17:11:39Z

Maxlmus: Maxlmus moved page ETL scenario language specification to ETL scenario language

2014-07-27T20:12:48Z

Maxlmus moved page ETL scenario language specification to ETL scenario language

Maxlmus at 20:11, 27 July 2014

2014-07-27T20:11:49Z

Maxlmus at 20:10, 27 July 2014

2014-07-27T20:10:20Z

Maxlmus at 20:09, 27 July 2014

2014-07-27T20:09:15Z

Maxlmus at 20:07, 27 July 2014

2014-07-27T20:07:48Z

Maxlmus at 20:05, 27 July 2014

2014-07-27T20:05:37Z

Maxlmus at 18:59, 27 July 2014

2014-07-27T18:59:37Z

@@ Line 109: / Line 109: @@
 <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<[[onpopulate]] [[action]]="save|skip"/></code><br>
 <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<[[source]]>linked source name</source></code><br>
-<code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<[[extract]] [[keyname]]="key name" [[keyfield]]="key fields"></code><br>
+<code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<[[extract]] [[limit]]="int" [[keyname]]="key name" [[keyfield]]="key fields"></code><br>
 <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<[[writer]] '''''[[class]]'''''="writer_class_name" [[attributes]] /></code><br>

← Older revision		Revision as of 17:11, 5 August 2014
Line 1:		Line 1:
−	~~{{FULLPAGENAME}}~~
−
	ETL scenarios must be written in XML-based language.		ETL scenarios must be written in XML-based language.

← Older revision		Revision as of 17:11, 5 August 2014
Line 1:		Line 1:
		+	{{FULLPAGENAME}}
		+
	ETL scenarios must be written in XML-based language.		ETL scenarios must be written in XML-based language.

← Older revision		Revision as of 20:11, 27 July 2014
Line 1:		Line 1:
−	ETL scenarios must be written in ~~special~~ XML-based language.	+	ETL scenarios must be written in XML-based language.

	== Language ==		== Language ==

@@ Line 13: / Line 13: @@
 == Language Artifacts ==
-* scenario - root node in XML. Used to define global attributes such as scenario name, description, script name, etc. Includes other nodes. Variables under scenario used to define global input parameters which can be used to parameterize scenario.
+* '''scenario''' - root node in XML. Used to define global attributes such as scenario name, description, script name, etc. Includes other nodes. Variables under scenario used to define global input parameters which can be used to parameterize scenario.
-* execute - root node for inner scenarios.
+* '''execute''' - root node for inner scenarios.
-* scenario - inner scenario under <execute>. Inner scenario is a sort of sub program executed as a part of owner's scenario.
+* '''scenario''' - inner scenario under <execute>. Inner scenario is a sort of sub program executed as a part of owner's scenario.
-* sources - root node for all sources.
+* '''sources''' - root node for all sources.
-* source - "extract from" object. Can include transformations and tasks which performed on the "extract from" object. Variables under source used to set dataset variables.
+* '''source''' - "extract from" object. Can include transformations and tasks which performed on the "extract from" object. Variables under source used to set dataset variables.
-* destinations - root node for all destinations.
+* '''destinations''' - root node for all destinations.
-* destination - "load into" object. Can include transformations and tasks which performed on the "load into" object. Variables under destination used to define destination columns.
+* '''destination''' - "load into" object. Can include transformations and tasks which performed on the "load into" object. Variables under destination used to define destination columns.
-* tasks - root node for tasks.
+* '''tasks''' - root node for tasks.
-* task - transformation performed on the source and destination or common task such as operation system command, etc. Variables under task used to define task parameters.
+* '''task''' - transformation performed on the source and destination or common task such as operation system command, etc. Variables under task used to define task parameters.
-* beforetasks - root node for tasks executed before first extract
+* '''beforetasks''' - root node for tasks executed before first extract
-* aftertasks - root node for tasks executed after last load
+* '''aftertasks''' - root node for tasks executed after last load
-* variables - root node for scenario, source, destination or task variables
+* '''variables''' - root node for scenario, source, destination or task variables
-* VARIABLE (UPPER-CASED variable name) - scenario's, source's, destination's or task's variable
+* '''VARIABLE''' (UPPER-CASED variable name) - scenario's, source's, destination's or task's variable
 == Rules ==

← Older revision	Revision as of 20:12, 27 July 2014
(No difference)

@@ Line 10: / Line 10: @@
 * Order of nodes in the node list matters. For examples if there are multiple <task> nodes under <tasks> they will be executed in order
 * For comments use <pre><!-- text --></pre>
 == Rules ==

@@ Line 24: / Line 24: @@
 * Attribute value "code" means that attribute value should be code in one of the supported scripting languages (for example JavaScript) or SQL
 * For boolean attributes "false|true" it is also possible to use (case insensitive) yes|no, y,|n, 1|0
-* empty|something or |something for node or attribute value means that there is a default value which is rarely getting changed so it is better to skip this node or attribute
+* '''empty|something''' or '''|something''' for node or attribute value means that there is a default value which is rarely getting changed so it is better to skip this node or attribute
 == ETL scenario parser ==