[
https://issues.apache.org/jira/browse/MINIFICPP-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270935#comment-16270935
]
ASF GitHub Bot commented on MINIFICPP-269:
------------------------------------------
Github user phrocker commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/157
@calebj I saw that your Travis imp run didn't build bustache, so I tried it
myself. I added global to the root env
https://github.com/phrocker/nifi-minifi-cpp/blob/ApplyTemplate/.travis.yml It
seemed to run and build it.
I then noticed Travis passed while my build continues to Fail. Would you be
okay adding A "Known Issues" referencing
https://bugs.llvm.org/show_bug.cgi?id=34298 in regards to bustache not building
on certain versions of os x? @apiri have any thoughts on this?
> 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)
