Namespace: |
|
Content: |
complex, 14 attributes, 3 elements |
Defined: |
globally in etl.xsd, see XML source |
Includes: |
definitions of 14 attributes and 3 elements |
Used: |
at 1 location |
XML Representation Summary | |||||
<... | |||||
batchColumn | = |
string | |||
batchSize | = |
nonNegativeInteger : "0" | |||
bulkLoad | = |
boolean | |||
columnDelimiter | = |
string | |||
dir | = |
string | |||
fileBaseName | = |
string | |||
fileExtension | = |
string | |||
queryName | = |
string | |||
quote | = |
string | |||
rowDelimiter | = |
string | |||
schemaName | = |
string | |||
targetOption | = |
("merge" | "append" | "truncate") : "append" | |||
type | = |
("query" | "file") : "query" | |||
useTransaction | = |
boolean : "true" | |||
> | |||||
|
|||||
</...> |
<complexType name="TargetObjectType"> <annotation> <documentation> Targets will be of type 'query' (the default), or 'file'. For query, the schemaName and queryName attributes are required. For file, the fileBaseName and fileExtension attributes are required. </documentation> </annotation> <all> </all> <annotation> <documentation> Bulk loads minimize the logging for auditing purposes and other overhead. </documentation> </annotation> </attribute> <annotation> <documentation> The base name to use for an output target file. Special substitutions: '${TransformRunId}' will be substituted with the transformRunId. '${Timestamp}' will be substituted with the timestamp at file creation. </documentation> </annotation> </attribute> <annotation> <documentation> Optional (required for pipeline usage), the extension for the output target file. A leading dot is optional; there will always be a dot separator between the file basename and extension </documentation> </annotation> </attribute> <annotation> <documentation> Character to qualify text when a field contains the column or row delimiter </documentation> </annotation> </attribute> <annotation> <documentation> Wrap writing to target query in a transaction. Not used when target is a file. </documentation> </annotation> </attribute> <annotation> <documentation> Formerly called "transactionSize". For query targets, incrementally commit target transaction every n rows instead of in a single wrapping transaction. For file targets, instead of writing a single file, create a new file every n rows. Each will be the fileBaseName + "-1", "-2", etc, + fileExtension </documentation> </annotation> </attribute> <annotation> <documentation> If specified, rather than count individual rows for the batchSize, use this as a sentinel field, and only increment the count of a current batch when the value in this field changes. If the name of the relevant column is being mapped via columnTransforms, use the target name, not the source name. </documentation> </annotation> </attribute> </complexType> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="batchColumn" type="string" use="optional"> <annotation> <documentation> If specified, rather than count individual rows for the batchSize, use this as a sentinel field, and only increment the count of a current batch when the value in this field changes. If the name of the relevant column is being mapped via columnTransforms, use the target name, not the source name. </documentation> </annotation> </attribute> |
Type: |
nonNegativeInteger, predefined |
Use: |
optional |
Default: |
"0" |
Defined: |
<attribute default="0" name="batchSize" type="nonNegativeInteger" use="optional"> <annotation> <documentation> Formerly called "transactionSize". For query targets, incrementally commit target transaction every n rows instead of in a single wrapping transaction. For file targets, instead of writing a single file, create a new file every n rows. Each will be the fileBaseName + "-1", "-2", etc, + fileExtension </documentation> </annotation> </attribute> |
Type: |
boolean, predefined |
Use: |
optional |
Defined: |
<attribute name="bulkLoad" type="boolean" use="optional"> <annotation> <documentation> Bulk loads minimize the logging for auditing purposes and other overhead. </documentation> </annotation> </attribute> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="columnDelimiter" type="string" use="optional"/> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="dir" type="string" use="optional"/> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="fileBaseName" type="string" use="optional"> <annotation> <documentation> The base name to use for an output target file. Special substitutions: '${TransformRunId}' will be substituted with the transformRunId. '${Timestamp}' will be substituted with the timestamp at file creation. </documentation> </annotation> </attribute> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="fileExtension" type="string" use="optional"> <annotation> <documentation> Optional (required for pipeline usage), the extension for the output target file. A leading dot is optional; there will always be a dot separator between the file basename and extension </documentation> </annotation> </attribute> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="queryName" type="string" use="optional"/> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="quote" type="string" use="optional"> <annotation> <documentation> Character to qualify text when a field contains the column or row delimiter </documentation> </annotation> </attribute> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="rowDelimiter" type="string" use="optional"/> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="schemaName" type="string" use="optional"/> |
Type: |
|
Use: |
optional |
Default: |
"append" |
Defined: |
<attribute default="append" name="targetOption" type="etl:TargetOptionType" use="optional"/> |
Type: |
|
Use: |
optional |
Default: |
"query" |
Defined: |
<attribute default="query" name="type" type="etl:TargetTypeType" use="optional"/> |
Type: |
boolean, predefined |
Use: |
optional |
Default: |
"true" |
Defined: |
<attribute default="true" name="useTransaction" type="boolean" use="optional"> <annotation> <documentation> Wrap writing to target query in a transaction. Not used when target is a file. </documentation> </annotation> </attribute> |
Type: |
etl:AlternateKeysType, complex content |
Defined: |
<element maxOccurs="1" minOccurs="0" name="alternateKeys" type="etl:AlternateKeysType"/> |
Type: |
etl:ColumnTransformsType, complex content |
Defined: |
<element maxOccurs="1" minOccurs="0" name="columnTransforms" type="etl:ColumnTransformsType"/> |
Type: |
etl:ConstantsType, complex content |
Defined: |
<element maxOccurs="1" minOccurs="0" name="constants" type="etl:ConstantsType"/> |
This XML schema documentation has been generated with DocFlex/XML RE 1.7.2 using DocFlex/XML XSDDoc 2.1.0 template set. DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML. DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-end XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future). A commercial license for "DocFlex/XML XSDDoc" will allow you:
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML SDK and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required! But this is not all. In addition to it, a commercial license for DocFlex/XML SDK will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own! Please note: By purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the result of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us! To buy a license, please follow this link: http://www.filigris.com/shop/ |