[
https://issues.apache.org/jira/browse/HIVE-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Sichi updated HIVE-1129:
-----------------------------
Attachment: HIVE-1129.1.patch
Here's a patch for getting/setting the variables in such a way that the
assertions are not triggered.
> Assertion in ExecDriver.execute when assertions are enabled in HADOOP_OPTS
> --------------------------------------------------------------------------
>
> Key: HIVE-1129
> URL: https://issues.apache.org/jira/browse/HIVE-1129
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.5.0
> Reporter: John Sichi
> Assignee: John Sichi
> Fix For: 0.6.0
>
> Attachments: HIVE-1129.1.patch
>
>
> I noticed that when running hive CLI, assertions are not enabled, which was
> causing me some confusion when debugging an issue.
> So, I added the following to my environment:
> export HADOOP_OPTS="-ea -esa"
> This worked, and allowed me to see assertion failures when executing via CLI.
> But then I tried to run a test, and got an assertion failure from the
> following code in ExecDriver.execute:
> // Turn on speculative execution for reducers
> HiveConf.setVar(job, HiveConf.ConfVars.HADOOPSPECULATIVEEXECREDUCERS,
> HiveConf.getVar(job, HiveConf.ConfVars.HIVESPECULATIVEEXECREDUCERS));
> The assertion says it should be using getBoolVar/setBoolVar instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.