I agree, but I meant just for the sake of getting a stable build for now. Besides, if we leave the Spark 1.3 upgrade, Hive will refuse to build, and Bigtop 1.0 can't be released like that, right? Can't really upgrade Spark without fixing Hive, unless Hive in Bigtop 1.0 gets bumped back to 1.0. So it's probably ideal both to keep the upgrade and to fix the Hive failure, as long as both can be done by the Bigtop 1.0 release, right?
BTW, the reason my team and I hadn't noticed this failure in Hive is that we currently have the Hive version set to 1.0 rather than 1.1 in our bigtop.mk. All Spark functionality (aka "Hive on Spark") was added in 1.1.0.
HIVE-9726 supposedly fixed the upgrade to Spark 1.3, so I'm trying to figure out why this failure is occurring. The fix version still just says "spark-branch", so it's unclear to me whether or not that fix was actually merged into Hive's 1.1 branch.