[jira] Commented: (HIVE-1129) Assertion in ExecDriver.execute when assertions are enabled in HADOOP_OPTS

["John Sichi (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829234#action_12829234 ] 

John Sichi commented on HIVE-1129:
----------------------------------

Here's the assertion stack:

    [junit] Exception in thread "main" java.lang.AssertionError
    [junit] 	at org.apache.hadoop.hive.conf.HiveConf.getVar(HiveConf.java:292)
    [junit] 	at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:569)
    [junit] 	at org.apache.hadoop.hive.ql.exec.ExecDriver.main(ExecDriver.java:946)


> 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.6.0
>            Reporter: John Sichi
>             Fix For: 0.6.0
>
>
> 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.