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

Bryan Bende commented on NIFI-1935:
-----------------------------------

The history on both branches (master and 0.x) shows the same two commits, with 
the last change back in September which would be several versions ago...

0.x:

https://github.com/apache/nifi/commits/0.x/nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/ConvertJSONToAvro.java

Master:

https://github.com/apache/nifi/commits/master/nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/ConvertJSONToAvro.java

> Added ConvertDynamicJsonToAvro processor
> ----------------------------------------
>
>                 Key: NIFI-1935
>                 URL: https://issues.apache.org/jira/browse/NIFI-1935
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>    Affects Versions: 1.0.0, 0.7.0
>            Reporter: Daniel Cave
>            Assignee: Alex Halldin
>            Priority: Minor
>             Fix For: 1.0.0, 0.7.0
>
>         Attachments: 
> 0001-NIFI-1935-Added-ConvertDynamicJSONToAvro.java.-Added.patch
>
>
> ConvertJsonToAvro required a predefined Avro schema to convert JSON and 
> required the presence of all field on the incoming JSON.  
> ConvertDynamicJsonToAvro functions similarly, however it now accepts the JSON 
> and schema as incoming flowfiles and creates the Avro dynamically.
> This processor requires the InferAvroSchema processor in its upstream flow so 
> that it can use the original and schema flowfiles as input.  These two 
> flowfiles will have the unique attribute inferredAvroId set on them by 
> InferAvroSchema so that they can be properly matched in 
> ConvertDynamicJsonToAvro.



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

Reply via email to