RecordSchemaCacheService
Implementation: VolatileSchemaCache
Specifies a Schema Cache to add the Record Schema to so that Record Readers can quickly lookup the schema. | Schema Protocol Version | schema-protocol-version | 1 | | The protocol version to be used for Schema Write Strategies that require a protocol version, such as Hortonworks Schema Registry strategies. Valid protocol versions for Hortonworks Schema Registry are integer values 1, 2, or 3. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)
This Property is only considered if the [Schema Write Strategy] Property is set to one of the following values: [HWX Schema Reference Attributes], [HWX Content-Encoded Schema Reference] |
Schema Access Strategy | schema-access-strategy | Inherit Record Schema | - Inherit Record Schema
- Use 'Schema Name' Property
- Use 'Schema Text' Property
| Specifies how to obtain the schema that is to be used for interpreting the data. |
Schema Registry | schema-registry | | Controller Service API: SchemaRegistry Implementations: ConfluentSchemaRegistry AmazonGlueSchemaRegistry HortonworksSchemaRegistry DatabaseTableSchemaRegistry AvroSchemaRegistry | Specifies the Controller Service to use for the Schema Registry
This Property is only considered if the [Schema Access Strategy] Property is set to one of the following values: [Use 'Schema Name' Property] |
Schema Name | schema-name | ${schema.name} | | Specifies the name of the schema to lookup in the Schema Registry property Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)
This Property is only considered if the [Schema Access Strategy] Property has a value of "Use 'Schema Name' Property". |
Schema Version | 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 (will be evaluated using flow file attributes and variable registry)
This Property is only considered if the [Schema Access Strategy] Property has a value of "Use 'Schema Name' Property". |
Schema Branch | 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 (will be evaluated using flow file attributes and variable registry)
This Property is only considered if the [Schema Access Strategy] Property has a value of "Use 'Schema Name' Property". |
Schema Text | schema-text | ${avro.schema} | | The text of an Avro-formatted Schema Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)
This Property is only considered if the [Schema Access Strategy] Property has a value of "Use 'Schema Text' Property". |
Date Format | 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 | 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 | 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). |
Pretty Print JSON | Pretty Print JSON | false | | Specifies whether or not the JSON should be pretty printed |
Suppress Null Values | suppress-nulls | Never Suppress | - Never Suppress
- Always Suppress
- Suppress Missing Values
| Specifies how the writer should handle a null field |
Allow Scientific Notation | Allow Scientific Notation | false | | Specifies whether or not scientific notation should be used when writing numbers |
Output Grouping | output-grouping | Array | - Array
- One Line Per Object
| Specifies how the writer should output the JSON records (as an array or one object per line, e.g.) Note that if 'One Line Per Object' is selected, then Pretty Print JSON must be false. |
Compression Format | compression-format | none | - none
- gzip
- bzip2
- xz-lzma2
- snappy
- snappy framed
- zstd
| The compression format to use. Valid values are: GZIP, BZIP2, ZSTD, XZ-LZMA2, LZMA, Snappy, and Snappy Framed |
Compression Level | compression-level | 1 | | The compression level to use; this is valid only when using GZIP compression. A lower value results in faster processing but less compression; a value of 0 indicates no compression but simply archiving
This Property is only considered if the [Compression Format] Property has a value of "gzip". |
State management:
This component does not store state.Restricted:
This component is not restricted.System Resource Considerations:
None specified.