[jira] [Commented] (MINIFI-36) Create mechanism that supports pull semantics for configuration changes

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user JPercivall opened a pull request:

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

    MINIFI-36 Refactoring config change notifiers and adding Pull config …

    …change notifier
    
    ### For all changes:
    - [X] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [X] Does your PR title start with MINIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [X] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [X] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi-minifi folder?
    - [X] Have you written or updated unit tests to verify your changes?
    - [X] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [X] If applicable, have you updated the LICENSE file, including the main LICENSE file under minifi-assembly?
    - [X] If applicable, have you updated the NOTICE file, including the main NOTICE file found under minifi-assembly?
    
    ### For documentation related changes:
    - [X] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


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

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

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

    https://github.com/apache/nifi-minifi/pull/51.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 #51
    
----
commit 6f4ebd751aca566097cdb19f2780fbf9ff1d4093
Author: Joseph Percivall <jo...@yahoo.com>
Date:   2016-10-06T20:27:19Z

    MINIFI-36 Refactoring config change notifiers and adding Pull config change notifier

----


> Create mechanism that supports pull semantics for configuration changes
> -----------------------------------------------------------------------
>
>                 Key: MINIFI-36
>                 URL: https://issues.apache.org/jira/browse/MINIFI-36
>             Project: Apache NiFi MiNiFi
>          Issue Type: Improvement
>          Components: Processing Configuration
>            Reporter: Aldrin Piri
>            Assignee: Joseph Percivall
>             Fix For: 0.1.0
>
>
> Much like the efforts of MINIFI-12, it would also be convenient for a configuration in which an instance could reach out to a defined endpoint to poll for changes and bring those into the associated bootstrap process to activate a change in processing.
> Considerations include the mechanism in which polling occurs and how this is exposed.  A way of knowing if the flow is new, likely bound to the efforts of MINIFI-35.  In one case, it is conceivable that an instance could reach out to a NiFi instance and its associated API to receive configuration. 



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