[
https://issues.apache.org/jira/browse/MINIFI-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302640#comment-15302640
]
ASF GitHub Bot commented on MINIFI-30:
--------------------------------------
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/17#discussion_r64796094
--- Diff:
minifi-bootstrap/src/main/java/org/apache/nifi/minifi/bootstrap/util/ConfigTransformer.java
---
@@ -616,15 +630,21 @@ private static void addConnection(final Element
parentElement, Map<String, Objec
addTextElement(element, "labelIndex", "1");
addTextElement(element, "zIndex", "0");
- addTextElement(element, "sourceId", "Processor");
+ addTextElement(element, "sourceId",
getValueString(connectionProperties, SOURCE_NAME_KEY));
--- End diff --
That is a very good way forward and I will refactor this to be two classes.
I'll look in to Kwalify and google a bit to see what others are using for YAML
schema validation.
> Improve Configuration to Allow Intermediate Processors
> ------------------------------------------------------
>
> Key: MINIFI-30
> URL: https://issues.apache.org/jira/browse/MINIFI-30
> Project: Apache NiFi MiNiFi
> Issue Type: Improvement
> Reporter: Joseph Percivall
> Assignee: Joseph Percivall
>
> Currently the config.yml spec and ConfigTransformer only allow for an input
> processor and S2S out. Going forward there needs to be a way to have
> intermediate processors to act on and route data, as well as a way to push
> data out using a processor (like PutMQTT) instead of S2S
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
