[
https://issues.apache.org/jira/browse/MAPREDUCE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726396#action_12726396
]
Jothi Padmanabhan commented on MAPREDUCE-623:
---------------------------------------------
bq. -1 for this since deprecated warnings in general should be fixed but not
ignored.
Sure, that is definitely the ideal way, but given that we are generating close
to 1000 deprecated warnings because of the move from Old to New API, it might
actually take a while before we could fix all of those. Should we blanket
disable them now and then reevaluate once the framework code has been updated
to use only New API objects?
> 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.
