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

ASF GitHub Bot commented on MINIFI-41:
--------------------------------------

Github user brosander commented on a diff in the pull request:

    https://github.com/apache/nifi-minifi/pull/21#discussion_r69166911
  
    --- Diff: 
minifi-commons/minifi-commons-schema/src/main/java/org/apache/nifi/minifi/commons/schema/BaseSchema.java
 ---
    @@ -15,13 +15,17 @@
      * limitations under the License.
      */
     
    -package org.apache.nifi.minifi.bootstrap.util.schema.common;
    +package org.apache.nifi.minifi.commons.schema;
     
     import java.lang.reflect.Constructor;
     import java.lang.reflect.InvocationTargetException;
    +import java.util.Collections;
    +import java.util.LinkedHashMap;
     import java.util.LinkedList;
     import java.util.List;
     import java.util.Map;
    +import java.util.Set;
    +import java.util.stream.Collectors;
     
     public class BaseSchema {
    --- End diff --
    
    So I agree that the toMap method is a little light atm, the one thing I 
liked about defining it in the superclass was to centralize the decision to use 
a LinkedHashMap (to preserve insertion order and allow YAML to have attributes 
in the desired order).
    
    I figured that it was possible we would want to add common attributes at 
the top level at some point in which case that would be a good place for it.
    
    In terms of the helper methods, I don't have a problem with making them 
static.


> Command Line Configuration Utility
> ----------------------------------
>
>                 Key: MINIFI-41
>                 URL: https://issues.apache.org/jira/browse/MINIFI-41
>             Project: Apache NiFi MiNiFi
>          Issue Type: New Feature
>            Reporter: Bryan Rosander
>
> It would really increase usability if we had a way to transform template xmls 
> into configuration YAML files for consumption by MiNiFi.
> The utility should:
> 1. Transform template xmls exported from NiFi into configuration YAML files.
> 2. Validate the contents of a given YAML file in the same way MiNiFi does at 
> runtime.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to