You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2016/07/04 18:38:10 UTC
[jira] [Commented] (MINIFI-36) Create mechanism that supports pull
semantics for configuration changes
[ https://issues.apache.org/jira/browse/MINIFI-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361693#comment-15361693 ]
Aldrin Piri commented on MINIFI-36:
-----------------------------------
Will need a more concrete centralized management point to fully scope and provide the needed details. Should be good target for next iteration and release.
> 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
> 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)