Common Properties of Writers
Writers are the final components of a transformation graph. They serve to write data to files located on disk or to send data using some FTP, LDAP or JMS connection, or insert data into database tables. Trash component, which discards all records it receives, is categorized as Writer as it can be set to store records in a debug file.
Each Writer must have at least one input port through which the data flows to this graph component from some of the others.
Writers can either append data to an existing file, sheet or database table, or replace the existing content by new one. For this purpose, Writers writing to files have the Append attribute. This attribute is set to false, by default. That means "do not append data, replace it". Replacing database table is available in some bulkloaders, e.g. in DB2BulkWriter.
You can also write data to one file or one database table by more Writers of the same graph; in such a case you should write data by different Writers in different phases.
Most Writers let you see some part of resulting data. Right-click the Writer and select the View data option. You will be prompted with the same View data dialog as when debugging the edges. For more details, see Viewing Debug Data. This dialog allows you to view the written data. It can only be used after graph has already been run.
Below is a brief overview of links to these options:
-
Below are examples of the File URL attribute for writing to local and remote files, through proxy, output port and dictionary:
-
As it has been shown in Defining Transformations, some Writers allow you to define a transformation. For information about transformation interfaces that must be implemented in transformations written in Java, see:
Component | Data output | Input ports | Output ports | Transformation | Transf. required | Java | CTL | Auto-propagated metadata |
---|---|---|---|---|---|---|---|---|
CloverDX binary file |
1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
- |
n |
n |
✓ |
⨯ |
✓ |
⨯ |
⨯ |
|
database |
1 |
0-2 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
database |
0-1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
.dbf file |
1 |
0 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
EDIFACT file |
1-n |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
emails |
0-1 |
0-2 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
flat file |
1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
Hadoop sequence file |
1 |
0 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
database |
1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
database |
0-1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
dictionary |
1-n |
0 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
dictionary |
1-n |
0 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
jms messages |
1 |
0 |
✓ |
⨯ |
✓ |
⨯ |
⨯ |
|
JSON file |
1-n |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
Kafka cluster |
1 |
0-2 |
✓ |
⨯ |
⨯ |
✓ |
✓ |
|
LDAP directory tree |
1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
database |
1 |
0-2 |
✓ |
✓ |
⨯ |
✓ |
✓ |
|
database |
0-1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
database |
0-1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
database |
0-1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
Parquet file |
1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
database |
0-1 |
0 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
QuickBase |
1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
QuickBase |
1 |
0-2 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
Salesforce |
1 |
2 |
✓ |
⨯ |
⨯ |
✓ |
✓ |
|
Salesforce |
1 |
2 |
✓ |
⨯ |
⨯ |
✓ |
✓ |
|
Salesforce |
1 |
2 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
XLS(X) file |
1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
Snowflake |
1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
✓ |
|
structured flat file |
1-3 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
.tde file |
1 |
0 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
none |
1 |
0 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
flat file |
1 |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
X12 file |
1-n |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |
|
XML file |
1-n |
0-1 |
⨯ |
⨯ |
⨯ |
⨯ |
⨯ |