[
https://issues.apache.org/jira/browse/MINIFICPP-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269107#comment-16269107
]
ASF GitHub Bot commented on MINIFICPP-269:
------------------------------------------
Github user calebj commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/157#discussion_r153566702
--- Diff: CMakeLists.txt ---
@@ -173,6 +173,12 @@ if (ENABLE_TENSORFLOW)
createExtension(TENSORFLOW-EXTENSIONS "TENSORFLOW EXTENSIONS" "This
enables TensorFlow support" "extensions/tensorflow"
"${TEST_DIR}/tensorflow-tests")
endif()
+## Bustache/template extensions
+option(ENABLE_BUSTACHE "Enables Bustache (ApplyTemplate) support." OFF)
--- End diff --
What with?
> 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)
