MapReduce (MAPREDUCE-3727) and Pig on Tez (PIG-4333) have implemented a work around to unset the mapreduce.job.credentials.binary property. Now hive has hit the same scenario this week (no jira yet that I see). While Tez dones generally handle mapreduce properties, should we provide a config cleaning helper that will help unify the config cleaning that will protect our users?
Jon
