[
https://issues.apache.org/jira/browse/NIFI-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328022#comment-15328022
]
Bryan Bende commented on NIFI-1935:
-----------------------------------
There will be releases made on both branches... the 0.7 release will be made in
the near future from the 0.x branch, and the 1.0.0 release will be made some
time later off master. The master branch has significant changes occurring on a
daily basis for the 1.0.0 release and is likely a bit unstable. Although
specifically for the ConvertJsonToAvro there is no difference between branches,
but there could be something else on the master branch causing problems.
Determining which tickets/changes go into each branch depends on the ticket...
for example, there is a complete rework of the UI taking place which is only
occurring on master. For other tickets like new processors or some bug fixes,
they are being merged to both branches. It is up to the submitter to indicate
the fix version on the JIRA to determine where they expect it to be committed
(both fix versions for both branches) and it is up to the reviewer to commit
the change on both branches. In some cases, it requires two patches or pull
requests if the code was developed for one branch, but requires changing code
that diverged from the other branch.
> 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)
