[ 
https://issues.apache.org/jira/browse/NIFI-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747634#comment-15747634
 ] 

ASF GitHub Bot commented on NIFI-751:
-------------------------------------

Github user avishsaha commented on the issue:

    https://github.com/apache/nifi/pull/70
  
    Hey @joewitt somehow I dont see AvroRecordConverter in NiFi's available 
Processors. I need to be able to convert an incoming source file (CSV/XML/JSON) 
to a generic schema. However, the problem is I am not sure how to - 1. Convert 
a AVRO 'record'  type to another and 2. When using ConvertAvroSchema how do we 
specify the dynamic properties as specified in the NiFi documentaion here - 
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.kite.ConvertAvroSchema/index.html
    
    Please advice. Thank you.


> Add Processor To Convert Avro Formats
> -------------------------------------
>
>                 Key: NIFI-751
>                 URL: https://issues.apache.org/jira/browse/NIFI-751
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 0.1.0
>            Reporter: Alan Jackoway
>            Assignee: Joseph Witt
>             Fix For: 0.3.0
>
>
> When working with data from external sources, such as complex WSDL, I 
> frequently wind up with complex nested data that is difficult to work with 
> even when converted to Avro format. Specifically, I often have two needs:
> * Converting types of data, usually from string to long, double, etc. when 
> APIs give only string data back.
> * Flattening data by taking fields out of nested records and putting them on 
> the top level of the Avro file.
> Unfortunately the Kite JSONToAvro processor only supports exact conversions 
> from JSON to a matching Avro schema and will not do data transformations of 
> this type. Proposed processor to come.
> Discussed this with [~rdblue], so tagging him here as I don't have permission 
> to set a CC for some reason.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to