You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andre F de Miranda (JIRA)" <ji...@apache.org> on 2017/05/07 06:34:04 UTC

[jira] [Updated] (NIFI-391) Need ability to deprecate components

     [ https://issues.apache.org/jira/browse/NIFI-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre F de Miranda updated NIFI-391:
------------------------------------
    Status: Patch Available  (was: In Progress)

> 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)