[
https://issues.apache.org/jira/browse/NIFI-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169129#comment-15169129
]
Jeremy Dyer commented on NIFI-1372:
-----------------------------------
[~chentecaliente] I do agree that the schema would be needed but to [~Toivo
Adams] point that can be pulled from incoming Avro data itself. The difficulty
comes from handling Avro complex types. The Avro primitive types can simply be
converted directly to CSV where the complex types would require some sort of
nested delimited fields approach
> Create ConvertAvroToCSV
> -----------------------
>
> Key: NIFI-1372
> URL: https://issues.apache.org/jira/browse/NIFI-1372
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 0.4.1
> Reporter: Jeremy Dyer
> Priority: Minor
>
> Currently there is no way to get from Avro to CSV. Certain processors like
> ExecuteSQL emit their results in the Avro format. While you can currently
> convert from Avro to JSON certain older systems will only accept CSV. Instead
> of adding the functionality to ExecuteSQL to emit CSV it makes sense to add a
> new processor that allows creating CSV from Avro in other places as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
