[
https://issues.apache.org/jira/browse/HADOOP-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199576#comment-17199576
]
Eric Badger commented on HADOOP-17169:
--------------------------------------
bq. I don't think we should go overboard and remove the old config key names.
This will be highly disruptive for future release adoption. We can mark them as
deprecated though, and consider removing them in a subsequent major release.
So this was my initial thought as well. But my concern is that we will
deprecate them now and like many other configs we will just leave them in
Hadoop forever. At what point is it acceptable to remove them? I suppose we
could deprecate them in the next release and remove them in the release after
that so as to have the "well, we gave you warning" argument. But I don't see it
being any less disruptive to the downstream users. If we're going to remove
them, it's going to be disruptive. It's whether we want to be disruptive now or
later.
> Remove whitelist/blacklist terminology from Hadoop Common
> ---------------------------------------------------------
>
> Key: HADOOP-17169
> URL: https://issues.apache.org/jira/browse/HADOOP-17169
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Eric Badger
> Assignee: Eric Badger
> Priority: Major
> Attachments: HADOOP-17169.001.patch, HADOOP-17169.002.patch,
> HADOOP-17169.003.patch
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
