Convert records from one Avro schema to another, including support for flattening and simple type conversions
avro, convert, kite
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| Input Schema | Input Schema | Avro Schema of Input Flowfiles. This can be a URI (dataset, view, or resource) or literal JSON schema. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| Output Schema | Output Schema | Avro Schema of Output Flowfiles. This can be a URI (dataset, view, or resource) or literal JSON schema. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| Locale | Locale | default | Locale to use for scanning data (see https://docs.oracle.com/javase/7/docs/api/java/util/Locale.html)or " default" for JVM default | |
| Compression type | kite-compression-type | SNAPPY |
| Compression type to use when writting Avro files. Default is Snappy. |
| Hadoop configuration Resources | Hadoop configuration files | A file or comma separated list of files which contains the Hadoop file system configuration. Without this, Hadoop will search the classpath for a 'core-site.xml' and 'hdfs-site.xml' file or will revert to a default configuration. This property expects a comma-separated list of file resources. Supports Expression Language: true (will be evaluated using variable registry only) |
Supports Sensitive Dynamic Properties: No
Dynamic Properties allow the user to specify both the name and value of a property.
| Name | Value | Description |
|---|---|---|
| Field name from input schema | Field name for output schema | Explicit mappings from input schema to output schema, which supports renaming fields and stepping into nested records on the input schema using notation like parent.id Supports Expression Language: false |
| Name | Description |
|---|---|
| success | Avro content that converted successfully |
| failure | Avro content that failed to convert |