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

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

GitHub user JPercivall opened a pull request:

    https://github.com/apache/nifi-minifi/pull/8

    MINIFI-15 Created a config file format with documentation, and a Util…

    … class to transform prospective config.yml into flow.xml and 
nifi.properties

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/JPercivall/nifi-minifi MINIFI-15

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi-minifi/pull/8.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #8
    
----
commit 345576f8d52f970cf9d74d0824879c3a90ffb0aa
Author: Joseph Percivall <joeperciv...@yahoo.com>
Date:   2016-03-30T18:14:15Z

    MINIFI-15 Created a config file format with documentation, and a Util class 
to transform prospective config.yml into flow.xml and nifi.properties

----


> Create Config Format, Documentation and Transformer
> ---------------------------------------------------
>
>                 Key: MINIFI-15
>                 URL: https://issues.apache.org/jira/browse/MINIFI-15
>             Project: Apache NiFi MiNiFi
>          Issue Type: Sub-task
>          Components: Processing Configuration
>            Reporter: Joseph Percivall
>             Fix For: 0.0.1
>
>
> To configure MiNiFi there needs to be a standard format for sending 
> information to the config change listeners. This needs to be fleshed out and 
> documented. 
> Also there should be a config transformer to facilitate going from the config 
> file to nifi.properties and flow.xml.gz.



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

Reply via email to