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

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

GitHub user JPercivall opened a pull request:

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

    MINIFI-12 initial commit of http config change notifier

    Created an http notifier that uses Jetty to listen for requests

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

    $ git pull https://github.com/JPercivall/nifi-minifi MINIFI-12-jetty-alone

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

    https://github.com/apache/nifi-minifi/pull/13.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 #13
    
----
commit 8d1bf82778112de5fb57a077b54dffd07ced71e3
Author: Joseph Percivall <[email protected]>
Date:   2016-04-14T23:01:54Z

    MINIFI-12 initial commit of http config change notifier

----


> Network based implementation
> ----------------------------
>
>                 Key: MINIFI-12
>                 URL: https://issues.apache.org/jira/browse/MINIFI-12
>             Project: Apache NiFi MiNiFi
>          Issue Type: Sub-task
>          Components: Data Format, Management, Processing Configuration
>            Reporter: Aldrin Piri
>            Assignee: Joseph Percivall
>             Fix For: 0.0.1
>
>
> As an initial proof of concept for providing centralized management it would 
> be advantageous to have configuration move beyond the file descriptor and 
> start happening from "remote" locations.  One way of doing this would be via 
> simple  web service from some control manager to the individual agents.  A 
> preliminary implementation could make use of a REST service to transmit 
> information and harness the work done in MINIFI-2 as the data format to 
> transfer the updates to processing.



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

Reply via email to