[
https://issues.apache.org/jira/browse/NIFI-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010462#comment-16010462
]
ASF subversion and git services commented on NIFI-391:
------------------------------------------------------
Commit d092551211afe300c3e08a017d6256cf268313b4 in nifi's branch
refs/heads/master from [~trixpan]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d092551 ]
NIFI-3761
- adjust testFullyDocumentedProcessor to correctly eval to false when needed
- Introduce the ability to deprecate a component
- Allow documentation to inform user about deprecation of a component
- This closes #1718
NIFI-391 - Add set/getDeprecationReson to DocumentedDTO and use it within
DtoFactory'
> Need ability to deprecate components
> ------------------------------------
>
> Key: NIFI-391
> URL: https://issues.apache.org/jira/browse/NIFI-391
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework, Core UI, Extensions
> Reporter: Mark Payne
> Assignee: Andre F de Miranda
>
> The API should allow processors to be marked as deprecated such that the UI
> then shows on the graph that the Processor is deprecated.
> Additionally, the UI should show in the Status Bar that there are deprecated
> components (processors, reporting tasks, controller services) in the flow.
> This valuable because of improvements such as NIFI-377. In this case, we have
> a community member making the Base64EncodeContent processor more generic so
> that it can encode/decode base 16,32, and 64. At this point,
> Base64EncodeContent doesn't make sense as a name, so there is a more generic
> EncodeContent processor. We don't need both, so we want to deprecated the
> Base64EncodeContent processor.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
