[ https://issues.apache.org/jira/browse/NIFI-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325212#comment-15325212 ]
Daniel Cave edited comment on NIFI-1935 at 6/10/16 8:32 PM: ------------------------------------------------------------ I'm going to do more testing around the existing processors then I will reply over the weekend or on Monday. There are some issues between verstions that I am working to track down and my original response may not be valid across the master/0.x split. I will respond Monday with a better answer. was (Author: daniel cave): I'm going to do more testing around the existing processors then I will reply over the weekend or on Monday. There are some issues between verstions that I am working to track down and my original response may not be valid across the master/0.x split (I was on a master version). I will respond Monday with a better answer. > 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)