[jira] [Commented] (NIFI-1053) Document the 'What if I change...' aspects of processor evolution

["Puspendu Banerjee (JIRA)" <ji...@apache.org>]

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

Puspendu Banerjee commented on NIFI-1053:
-----------------------------------------

Is this ticket still valid and is there anyone working on this?

> 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
>            Assignee: Joseph Percivall
>
> 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)