[
https://issues.apache.org/jira/browse/NIFI-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003565#comment-16003565
]
ASF GitHub Bot commented on NIFI-391:
-------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1718
Ok sounds good. Let's proceed with this PR and then we can file another
JIRA for the UI work.
I just started reviewing and noticed that the `DocumentTypeDTO` is missing
the deprecation flag. Once the field has been added it will need to be set in
the `DtoFactory`. This will be needed for the new [Processor|Controller
Service|Reporting Task] dialogs.
Thanks
> 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)
