[
https://issues.apache.org/jira/browse/NIFI-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059534#comment-16059534
]
Matt Burgess commented on NIFI-3000:
------------------------------------
As of NIFI-1280 (NiFi 1.2.0), the current version of Avro used is 1.8.1. The
record-aware processors can handle logical types, and via NIFI-2624 (NiFi
1.3.0), the JDBC-to-Avro processors (ExecuteSQL, QueryDatabaseTable, e.g.) can
support logical types as well. However the remaining Avro processors may or may
not support logical types (based on whether the incoming schema contains
logical types and the processor conserves the schema):
- SplitAvro
- ConvertAvroSchema
- ConvertAvroToORC
- ConvertAvroToJSON
- ConvertJSONToAvro
- ConvertCSVToAvro
- InferAvroSchema
Much of the benefit of Avro is gained when having multiple records in one file,
so I'd be fine with lowering the priority of this Jira or closing as Won't Fix,
provided an InferRecordSchema is implemented (NIFI-4109).
> Avro processors should support logical types
> --------------------------------------------
>
> Key: NIFI-3000
> URL: https://issues.apache.org/jira/browse/NIFI-3000
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
>
> Most/All of the Avro processors cannot currently handle logical types such as
> fixed and date types. The current version of Avro used is 1.7.7, which only
> supports decimal and fixed logical types
> (https://avro.apache.org/docs/1.7.7/spec.html#Logical+Types). If this version
> is to be retained, then support for decimal and fixed logical types should be
> added wherever possible.
> However I think a better option is to upgrade to Avro 1.8.x and support all
> the corresponding logical types
> (https://avro.apache.org/docs/1.8.0/spec.html#Logical+Types). This would
> involve regression testing and possibly breaking changes (although hopefully
> not from the user perspective).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
