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

Junping Du commented on MAPREDUCE-6814:
---------------------------------------

Hi [~boky01], I just add you into contributor list.
For this particular issue, I have no strong idea to deprecate it or not as 
MapReduce API (old or new) has long history and there is no significant effort 
recently to improve/change it. I don't see the significant gain we get from 
this change unless I miss something important.

> mapred's FileAlreadyExistsException should be deprecated in favor of 
> hadoop-common's one.
> -----------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6814
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6814
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Andras Bokor
>            Assignee: Andras Bokor
>            Priority: Minor
>
> Mapred's FileAlreadyExistsException was deprecated with MAPREDUCE-963 but 
> later on it was un-deprecate with MAPREDUCE-1735/MAPREDUCE-3771.
> It think it was un-deprecate by mistake:
> # MAPREDUCE-963 un-deprecate FAEE
> # Later on the whole Mapreduce 1 API was deprecated
> # By MAPREDUCE-1735/MAPREDUCE-3771 Mapred 1 API (including FAEE) was 
> un-deprecated.
> Since FAEE was deprecated regardless of point 2 it shouldn't have been 
> un-deprecated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org

Reply via email to