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 |
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 |
Include Header Line | true | | Specifies whether or not the CSV column names should be written out as the first line. |
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 |
Quote Mode | MINIMAL | - Quote All Values
- Quote Minimal
- Quote Non-Numeric Values
- Do Not Quote Values
| Specifies how fields should be quoted when they are written |
Record Separator | \n | | Specifies the characters to use in order to separate CSV Records |
Include Trailing Delimiter | false | | If true, a trailing delimiter will be added to each CSV Record that is written. If false, the trailing delimiter will be omitted. |
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.