SchemaRegistry
Implementations: AvroSchemaRegistry
ConfluentSchemaRegistry
HortonworksSchemaRegistry
Specifies the Controller Service to use for the Schema Registry | Schema Name | ${schema.name} | | Specifies the name of the schema to lookup in the Schema Registry property Supports Expression Language: true |
Schema Version | | | Specifies the version of the schema to lookup in the Schema Registry. If not specified then the latest version of the schema will be retrieved. Supports Expression Language: true |
Schema Branch | | | Specifies the name of the branch to use when looking up the schema in the Schema Registry property. If the chosen Schema Registry does not support branching, this value will be ignored. Supports Expression Language: true |
Schema Text | ${avro.schema} | | The text of an Avro-formatted Schema Supports Expression Language: true |
CSV Parser | commons-csv | - Apache Commons CSV
- Jackson CSV
| Specifies which parser to use to read CSV records. NOTE: Different parsers may support different subsets of functionality and may also exhibit different levels of performance. |
Date Format | | | Specifies the format to use when reading/writing Date fields. If not specified, Date fields will be assumed to be number of milliseconds since epoch (Midnight, Jan 1, 1970 GMT). If specified, the value must match the Java Simple Date Format (for example, MM/dd/yyyy for a two-digit month, followed by a two-digit day, followed by a four-digit year, all separated by '/' characters, as in 01/01/2017). |
Time Format | | | Specifies the format to use when reading/writing Time fields. If not specified, Time fields will be assumed to be number of milliseconds since epoch (Midnight, Jan 1, 1970 GMT). If specified, the value must match the Java Simple Date Format (for example, HH:mm:ss for a two-digit hour in 24-hour format, followed by a two-digit minute, followed by a two-digit second, all separated by ':' characters, as in 18:04:15). |
Timestamp Format | | | Specifies the format to use when reading/writing Timestamp fields. If not specified, Timestamp fields will be assumed to be number of milliseconds since epoch (Midnight, Jan 1, 1970 GMT). If specified, the value must match the Java Simple Date Format (for example, MM/dd/yyyy HH:mm:ss for a two-digit month, followed by a two-digit day, followed by a four-digit year, all separated by '/' characters; and then followed by a two-digit hour in 24-hour format, followed by a two-digit minute, followed by a two-digit second, all separated by ':' characters, as in 01/01/2017 18:04:15). |
CSV Format | custom | - Custom Format
- RFC 4180
- Microsoft Excel
- Tab-Delimited
- MySQL Format
- Informix Unload
- Informix Unload Escape Disabled
| Specifies which "format" the CSV data is in, or specifies if custom formatting should be used. |
Value Separator | , | | The character that is used to separate values/fields in a CSV Record |
Treat First Line as Header | false | | Specifies whether or not the first line of CSV should be considered a Header or should be considered a record. If the Schema Access Strategy indicates that the columns must be defined in the header, then this property will be ignored, since the header must always be present and won't be processed as a Record. Otherwise, if 'true', then the first line of CSV data will not be processed as a record and if 'false',then the first line will be interpreted as a record. |
Ignore CSV Header Column Names | false | | If the first line of a CSV is a header, and the configured schema does not match the fields named in the header line, this controls how the Reader will interpret the fields. If this property is true, then the field names mapped to each column are driven only by the configured schema and any fields not in the schema will be ignored. If this property is false, then the field names found in the CSV Header will be used as the names of the fields. |
Quote Character | " | | The character that is used to quote values so that escape characters do not have to be used |
Escape Character | \ | | The character that is used to escape characters that would otherwise have a specific meaning to the CSV Parser. |
Comment Marker | | | The character that is used to denote the start of a comment. Any line that begins with this comment will be ignored. |
Null String | | | Specifies a String that, if present as a value in the CSV, should be considered a null field instead of using the literal value. |
Trim Fields | true | | Whether or not white space should be removed from the beginning and end of fields |
Character Set | UTF-8 | | The Character Encoding that is used to encode/decode the CSV file Supports Expression Language: true |
State management:
This component does not store state.Restricted:
This component is not restricted.System Resource Considerations:
None specified.