[jira] [Commented] (MINIFICPP-357) Upgrade YAML parsing to support version 3 of the config schema and work with later toolkits

["Aldrin Piri (JIRA)" <ji...@apache.org>]

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

Aldrin Piri commented on MINIFICPP-357:
---------------------------------------

Should also tackle handling the update to targetIdentifer coming out in 1.5 when available.  For the Java implementation this is covered in https://issues.apache.org/jira/browse/MINIFI-421.

The client dto libraries in Java handle this process but in C++ we will need to provide this logic.

https://issues.apache.org/jira/browse/NIFI-4719 provided an encoding version of 1.2 to identify templates that made use of the new targetIdentifer.  If that is the encodingVersion, that is the UUID we should attempt connection.

> Upgrade YAML parsing to support version 3 of the config schema and work with later toolkits
> -------------------------------------------------------------------------------------------
>
>                 Key: MINIFICPP-357
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-357
>             Project: NiFi MiNiFi C++
>          Issue Type: Improvement
>            Reporter: Aldrin Piri
>            Assignee: Andrew Christianson
>
> Currently minificpp makes use of what is effectively YAML, v1 and requires the usage of the 0.0.1 toolkit to perform transformations.  We should get these in sync across agent implementations and allow users to make use of one toolkit for performing transformations.
> Scope involves mapping v3 config to what is currently supported. Not all features in reference config files (e.g. dynamic properties) are yet supported in MiNiFi. Support of those features is out of scope.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)