nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Bress (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-391) Need ability to deprecate components
Date Wed, 18 Mar 2015 18:04:38 GMT

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

Dan Bress commented on NIFI-391:
--------------------------------

Mark,
   Good call on not using java.lang.Deprecated... I got confused, the javadoc annotation supports
"deprecated in favor of..." but the Java annotation does not.  Lame.

   I don't have any ideas for what it should be called, but I agree it needs a description,
and an optional link for a replacement.

> 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
>             Fix For: 0.2.0
>
>
> 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.4#6332)

Mime
View raw message