You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2016/07/12 16:27:20 UTC

[jira] [Updated] (NIFI-1935) Added ConvertDynamicJsonToAvro processor

     [ https://issues.apache.org/jira/browse/NIFI-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Witt updated NIFI-1935:
------------------------------
    Fix Version/s:     (was: 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
>         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)