[jira] [Commented] (NIFI-2357) Component hot deployment

["Joseph Witt (JIRA)" <ji...@apache.org>]

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

Joseph Witt commented on NIFI-2357:
-----------------------------------

certainly a good idea.  Related to the following proposals

https://cwiki.apache.org/confluence/display/NIFI/Extension+Repositories+%28aka+Extension+Registry%29+for+Dynamically-loaded+Extensions

https://cwiki.apache.org/confluence/display/NIFI/Configuration+Management+of+Flows



> Component hot deployment
> ------------------------
>
>                 Key: NIFI-2357
>                 URL: https://issues.apache.org/jira/browse/NIFI-2357
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core Framework
>            Reporter: n h
>              Labels: Deployment, Hot
>
> Hot deployment of new/upgraded components is a critical requirement in many scenarios. A few suggestions are :
> 1. Hot deployment of new processors/components 
> 2. Hot deployment of processors/components that are not used in current flow context
> 3. Rolling upgrades (in a cluster)
> "Hot deployment of new processors" has immediate benefits. For example it helps in two very common scenarios :
> a) Development of a complex processor that uses a few nifi services (where mock framework only helps partially). (might be simple in a single node!) .
> b) Complex system that can't be restarted (Or has very short maintenance time : a few hours each month/year). In this situation we could build "upgraded processor" and use them as "new processor".



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