SchemaRegistry
Implementations: DatabaseTableSchemaRegistry
HortonworksSchemaRegistry
ConfluentSchemaRegistry
AvroSchemaRegistry
AmazonGlueSchemaRegistry
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: [Confluent Content-Encoded Schema Reference], [Use 'Schema Name' Property], [HWX Schema Reference Attributes], [HWX Content-Encoded Schema Reference] | 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". |
Schema Inference Cache | schema-inference-cache | | Controller Service API: RecordSchemaCacheService Implementation: VolatileSchemaCache | Specifies a Schema Cache to use when inferring the schema. If not populated, the schema will be inferred each time. However, if a cache is specified, the cache will first be consulted and if the applicable schema can be found, it will be used instead of inferring the schema.
This Property is only considered if the [Schema Access Strategy] Property has a value of "Infer Schema". |
Starting Field Strategy | starting-field-strategy | Root Node | - Root Node
- Nested Field
| Start processing from the root node or from a specified nested node. |
Starting Field Name | starting-field-name | | | Skips forward to the given nested JSON field (array or object) to begin processing.
This Property is only considered if the [Starting Field Strategy] Property has a value of "Nested Field". |
Schema Application Strategy | schema-application-strategy | Selected Part | - Whole JSON
- Selected Part
| Specifies whether the schema is defined for the whole JSON or for the selected part starting from "Starting Field Name".
This Property is only considered if all of the following conditions are met:- The [Schema Access Strategy] Property is set to one of the following values: [Confluent Content-Encoded Schema Reference], [Use 'Schema Name' Property], [Use 'Schema Text' Property], [HWX Schema Reference Attributes], [HWX Content-Encoded Schema Reference]
- The [Starting Field Strategy] Property has a value of "Nested Field".
|
Max String Length | Max String Length | 20 MB | | The maximum allowed length of a string value when parsing the JSON document |
Allow Comments | Allow Comments | false | | Whether to allow comments when parsing the JSON document |
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). |
State management:
This component does not store state.Restricted:
This component is not restricted.System Resource Considerations:
None specified.See Also:
JsonPathReader