[jira] [Commented] (MINIFICPP-269) Implement ApplyTemplate processor

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on MINIFICPP-269:
------------------------------------------

Github user phrocker commented on the issue:

    https://github.com/apache/nifi-minifi-cpp/pull/157
  
    @calebj If you rebase from master you'll see the bootstrap script. Cherry pick this: https://github.com/NiFiLocal/nifi-minifi-cpp/commit/4b516704bf66036613e4ea5a9ec776dd0fff0b2c
    
    You should then (hopefully) have a green travis, and anyone building through the bootstrap will not be able to enable bustache when they have the version of gcc in which this bug exists. 


> Implement ApplyTemplate processor
> ---------------------------------
>
>                 Key: MINIFICPP-269
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-269
>             Project: NiFi MiNiFi C++
>          Issue Type: New Feature
>            Reporter: Caleb Johnson
>            Priority: Minor
>              Labels: mustache, processor, template, templates
>             Fix For: 0.4.0
>
>
> The ApplyTemplate processor is fairly straightforward: it reads a [mustache|https://mustache.github.io/] template from a provided path on disk and maps flowfile attributes to template values.
> Dynamic properties (MINIFI-171) would go a long way towards making these templates more flexible by using the union of input flowfile attributes and (possibly evaluated?) properties as the value map.
> Due to its dependency on [bustache|https://github.com/jamboree/bustache] and boost, it has been made into an optional extension, much like the libarchive processors have.
> It may also be desirable to load the template from the input flowfile's contents instead of a configurable path.



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