[
https://issues.apache.org/jira/browse/NIFI-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330081#comment-15330081
]
Joseph Percivall commented on NIFI-1935:
----------------------------------------
[~bende] is referring to the 1.0.0 release and the 0.7.0 release which tickets
are tagged "0.7.0" and "1.0.0" in Jira. The 1.0.0 release (scheduled for later
in the summer) will be based on the master branch. The 0.7.0 release is
currently being finalized from the 0.x branch. It sounds like the patches
1933-1935 have a not insignificant amount of development that need to be done
and since we're hoping to cut a release client this week for 0.7.0, are you ok
with sliding these changes to just be incorporated into 1.0.0?
> 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,
> GetFileSplitInferConvertAvro.xml, SampleWell.json
>
>
> 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)
