I am not at all happy with this being a blocker. First off let me point out that I seem to ALWAYS get held to a higher standard then everyone else. For example, https://issues.apache.org/jira/browse/HIVE-1335 it was insisted that I use IVY. Yet with https://issues.apache.org/jira/browse/HIVE-1235 obviously no such rule was enforced here.
As you pointed out:
The HBase problems were part of what caused Hive continuous integration to go broken for many weeks. The failure frequency was very high due to conflicts from unrelated port-hungry services being run on committer dev boxes.
So in other words, the hbase-handler was allowed to go +1 and break the hudson/jenkins for weeks, until someone got around to finding a solution, but now this same reason this will go -1 and not get committed.
Upstream Hadoop !Unable to render embedded object: File (NEVER) not found.! completes a full 'ant test' successfully. While this is not an ideal situation it is a fact.
Also the one week lag time between patch-available and review just to find one new blocker at a time is getting old. I think I have seen 15 issues get reviewed and committed since this went patch_available.