CloudConnectDataWriter
We assume that you have already learned what is described in:
If you want to find the right Writer for your purposes, see Writers Comparison.
Short Summary
CloudConnectDataWriter writes data to files in our internal binary CloudConnect data format.
| Component | Data output | Input ports | Output ports | Transformation | Transf. required | Java | CTL |
|---|---|---|---|---|---|---|---|
| CloudConnectDataWriter | CloudConnect binary file | 1 | 0 | no | no | no | no |
Abstract
CloudConnectDataWriter writes data to files (local or remote) in our internal binary CloudConnect data format. It can also compress output files, write data to console, or dictionary.
![[Note]](figures/note.png) | Note |
|---|---|
Since 2.9 version of CloudConnect CloudConnectDataWriter writes also a header to output files with the version number. For this reason, CloudConnectDataReader expects that files in CloudConnect binary format contain such a header with the version number. CloudConnectDataReader 2.9 cannot read files written by older versions of CloudConnect nor these older versions can read data written by CloudConnectDataWriter 2.9. |
Icon
Ports
| Port type | Number | Required | Description | Metadata |
|---|---|---|---|---|
| Input | 0 | yes | For received data records | Any |
CloudConnectDataWriter Attributes
| Attribute | Req | Description | Possible values |
|---|---|---|---|
| Basic | |||
| File URL | yes | Attribute specifying where received data will be written (CloudConnect data file, console, dictionary). See Supported File URL Formats for Writers. See also Output File Structure for more information. | |
| Append | By default, new records overwrite the older ones. If
set to true, new records are appended to
the older records stored in the output file(s). | false (default) | true | |
| Save metadata | By default, no file with metadata definition is saved.
If set to true, metadata is saved to
metadata file. See Output File Structure for more
information. | false (default) | true | |
| Save index 1) | By default, no file with indices of records is saved.
If set to true, the index of records is
saved to an index file. See Output File Structure for more
information. | false (default) | true | |
| Advanced | |||
| Create directories | By default, non-existing directories are not created.
If set to true, they are created. | false (default) | true | |
| Compress level | Sets the compression level. By default, zip compression
level is used. Level 0 means archiving
without compression. | -1 (default) | 0-9 | |
| Number of skipped records | Number of records to be skipped. See Selecting Output Records. | 0-N | |
| Max number of records | Maximum number of records to be written to the output file. See Selecting Output Records. | 0-N | |
Legend:
1) Please note this is a deprecated attribute.
Advanced Description
Output File Structure
Non-Archived Output File(s)
If you do not archive and/or compress the created file(s), the output file(s) will be saved separately with the following name(s):
filename(for the file with data),filename.idx(for the file with index) andfilename.fmt(for the file with metadata). In all of the created name(s),filenamecontains its extension (if it has any) in all of these three created file(s) names.Archived Output File(s)
If the output file is archived and/or compressed (independently on the type of the file), it has the following internal structure:
DATA/filename,INDEX/filename.idxandMETA/filename.fmt. Here,filenameincludes its extension (if it has any) in all of these three names.Example 54.1. Internal Structure of Archived Output File(s)
DATA/employees.clv,INDEX/employees.clv.idx,META/employees.clv.fmt.