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

Joseph Percivall commented on NIFI-1053:
----------------------------------------

[[email protected]] it is definitely still valid but I don't believe 
anyone is working on it. I had wanted to get around to it but got busy with 
other developments. If anyone has some bandwidth to tackle this, that would be 
awesome.

> Document the 'What if I change...' aspects of processor evolution
> -----------------------------------------------------------------
>
>                 Key: NIFI-1053
>                 URL: https://issues.apache.org/jira/browse/NIFI-1053
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Documentation & Website
>            Reporter: Alan Jackoway
>
> Alan brought up a strong point on the dev thread.  That is basically that it 
> is unclear today or not well documented what the mindset for a developer 
> can/should be or a user can/should be in the presence of a variety of 
> scenarios of processor/extension changes.  The questions that follow are 
> oriented around processors.  But we must do this for all extension types.
> But I agree with you that we should make this a fully documented concept in 
> the developer guide (so they know what they can/cannot do) and possibly the 
> user guide (so they know what was done to them).  We need to cover at least:
> - I want to change the processor class name
> - I want to change the processor package name
> - I want to add processor relationships
> - I want to remove processor relationships
> - I want to add processor properties
> - I want to remove processor properties
> - I want to change a required property to optional
> - I want to change an optional property to required
> - I want to change the display name of a property
> - I want to change the behavior of a processor that could have different side 
> effects despite the same configuration



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

Reply via email to