[jira] [Updated] (MINIFICPP-357) Upgrade YAML parsing to support version 3 of the config schema and work with later toolkits
[ https://issues.apache.org/jira/browse/MINIFICPP-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Christianson updated MINIFICPP-357: -- Description: 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. was: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. > 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)
[jira] [Updated] (MINIFICPP-357) Upgrade YAML parsing to support version 3 of the config schema and work with later toolkits
[ https://issues.apache.org/jira/browse/MINIFICPP-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-357: -- Attachment: 1.4-Template.xml 1.5-Template.xml > 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 > Attachments: 1.4-Template.xml, 1.5-Template.xml > > > 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)
[jira] [Updated] (MINIFICPP-357) Upgrade YAML parsing to support version 3 of the config schema and work with later toolkits
[ https://issues.apache.org/jira/browse/MINIFICPP-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-357: -- Status: Patch Available (was: Open) > 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 > Attachments: 1.4-Template.xml, 1.5-Template.xml > > > 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)
[jira] [Updated] (MINIFICPP-357) Upgrade YAML parsing to support version 3 of the config schema and work with later toolkits
[ https://issues.apache.org/jira/browse/MINIFICPP-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-357: -- Fix Version/s: 0.4.0 > 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 > Fix For: 0.4.0 > > Attachments: 1.4-Template.xml, 1.5-Template.xml > > > 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)
[jira] [Updated] (MINIFICPP-357) Upgrade YAML parsing to support version 3 of the config schema and work with later toolkits
[ https://issues.apache.org/jira/browse/MINIFICPP-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-357: -- Resolution: Fixed Status: Resolved (was: Patch Available) > 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 > Fix For: 0.4.0 > > Attachments: 1.4-Template.xml, 1.5-Template.xml > > > 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)
