hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andras Bokor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6814) mapred's FileAlreadyExistsException should be deprecated in favor of hadoop-common's one.
Date Wed, 14 Dec 2016 21:20:58 GMT

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

Andras Bokor commented on MAPREDUCE-6814:
-----------------------------------------

[~djp], what do you think about this?

> 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: Boris Shkolnik
>            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
> which is a mistake because 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org


Mime
View raw message