Argh.. I was trying to see if we should hold of this commit. I just woke up to realize that trunk is being rebased as release 0.21. Given this, and the fact that the job-acls feature a.k.a
MAPREDUCE-1307 is still only 'half-complete' because of MAPREDUCE-1664 and other related minor issues. I checked with Ravi who started working on MAPREDUCE-1664 and came to know that it will not be possible to get it in by freeze date(30th?) because it involves some consensus building as well as some time for implementation.
Two things can be done. Complete
MAPREDUCE-1664 by marking it as a blocker. For this we will need to know the release time lines for 0.21. Or consider job-acls as an unstable feature and undocument it from mapred-default.xml and forrest. The later is a plausibility not just because of MAPREDUCE-1664, but also due to other subsequent issues that arose out of this feature that we found out in internal discussions/testing. Thoughts?
BTW, there must be a lot of 'half-features' like these which are originally being worked upon for 0.22 but will fall back into 0.21 because of the recent decision. For e.g.,
HADOOP-6568 which has become 'unstable' due to uncertainty of MAPREDUCE-1542 and HDFS-1008.
What is the community thinking about these issues? Will need to shoot an email on general mailing list, I guess.