> ... 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.