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

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

Github user joewitt commented on the pull request:

    https://github.com/apache/incubator-nifi/pull/70#issuecomment-121215127
  
    @rdblue You might want to double check the CSV and JSON to Avro processors 
and add documentation to them like Alan has done here (additional 
documentation).  Providing an example of usage could be a big help to folks.   
Also please verify whether your processor needs to accept the hadoop 
configuration.  If not you can simply remove it from the properties being added.
    
    @jackowaya Great job!  I've made a small change to remove the pulling in of 
the hadoop configuration property.  


> 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
>
> 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