You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/10/22 04:03:27 UTC
[jira] [Created] (NIFI-1053) Document the 'What if I change...'
aspects of processor evolution
Joseph Witt created NIFI-1053:
---------------------------------
Summary: 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
Fix For: 0.4.0
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)