[
https://issues.apache.org/jira/browse/MAPREDUCE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726669#action_12726669
]
Tsz Wo (Nicholas), SZE commented on MAPREDUCE-623:
--------------------------------------------------
> ... Should we blanket disable them now and then reevaluate once the framework
> code has been updated to use only New API objects?
test-patch.sh is shared by common, hdfs and mapreduce. So I am -1 on changing
it for a mapreduce specific problem.
I agree that it is hard to fix 1000 deprecated warnings at once. It may be
good to disable the checking in mapreduce as a temporary fix. I suggest that
the deprecated warnings should be shown somewhere even they are disabled.
Otherwise, it will be hard to keep track of them.
> Resolve javac warnings in mapred
> --------------------------------
>
> Key: MAPREDUCE-623
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-623
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Jothi Padmanabhan
> Assignee: Jothi Padmanabhan
> Attachments: mapreduce-623.patch
>
>
> Towards a solution for HADOOP-5628, we need to resolve all javac warnings.
> This jira will try to resolve javac warnings where ever possible and suppress
> them where resolution is not possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
