[
https://issues.apache.org/jira/browse/NIFI-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367471#comment-14367471
]
Dan Bress commented on NIFI-391:
--------------------------------
Mark, do you envision using regular old
[java.lang.Deprecated|http://docs.oracle.com/javase/7/docs/api/java/lang/Deprecated.html]
to indicate that a component is deprecated? That would be my vote, rather
than creating a new way of doing this.
Should this apply to Processors, ControllerServices, and Reporting Tasks? I
vote yes.
Should it apply to any of the other extension points? I'd vote yes, but be
find with this as a down the road item.
Should this apply to Properties on a ConfigurableComponent? I'd vote no, this
might open up a can of worms
Should this apply to Relationships on Processors? I'd vote vote no as well
> 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)
