[
https://issues.apache.org/jira/browse/MINIFICPP-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225976#comment-16225976
]
ASF GitHub Bot commented on MINIFICPP-269:
------------------------------------------
Github user phrocker commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/157#discussion_r147566485
--- Diff: libminifi/CMakeLists.txt ---
@@ -56,6 +56,7 @@
include_directories(../thirdparty/yaml-cpp-yaml-cpp-20171024/include)
include_directories(../thirdparty/civetweb-1.9.1/include)
include_directories(../thirdparty/jsoncpp/include)
include_directories(../thirdparty/concurrentqueue/)
+include_directories(../thirdparty/bustache/include)
--- End diff --
You shouldn't need to include this here, but rather in the your extension's
CMakeLists
> 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
>
> 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)
