You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/08 22:16:25 UTC

[jira] [Commented] (MINIFI-2) File based implementation

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

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

GitHub user apiri opened a pull request:

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

    MINIFI-2 MINIFI-4 Configuration change notifier and listener

    MINIFI-2
    MINIFI-4
    Providing Configuration change notifier and listener interfaces with accompanying File implementation.

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

    $ git pull https://github.com/apiri/nifi-minifi MINIFI-4

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

    https://github.com/apache/nifi-minifi/pull/7.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 #7
    
----
commit 50ed9bf9ad86729379f72b8d5f2c694244764054
Author: Aldrin Piri <al...@apache.org>
Date:   2016-04-08T18:59:58Z

    MINIFI-2 MINIFI-4 Establishing a base implementation of the configuration change listener and notification services as well as a File implementation.

----


> File based implementation
> -------------------------
>
>                 Key: MINIFI-2
>                 URL: https://issues.apache.org/jira/browse/MINIFI-2
>             Project: Apache NiFi MiNiFi
>          Issue Type: Sub-task
>          Components: Processing Configuration
>            Reporter: Aldrin Piri
>             Fix For: 0.0.1
>
>         Attachments: ConfigFileExplanation.xml, Properties_Guide.md, config.yml
>
>
> A defined schema for processing configuration will need to be defined.  XML or YAML seem like possible options for achieving this.
> Agent configuration will come from two places, a bootstrap properties file and a flow configuration file. The bootstrap will make use of some of the original nifi.properties in order to start up the agent. The flow configuration file will essentially be a stripped down version of a flow.xml (with potentially S2S properties from nifi.properties).
> The format for the bootstrap.properties should likely be similar to nifi.properties. 
> Further, a way to incorporate this to leverage the libraries from core NiFi will aid in achieving a proof of concept implementation more expediently.



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