[
https://issues.apache.org/jira/browse/HIVE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698611#action_12698611
]
Namit Jain commented on HIVE-372:
---------------------------------
the .2 patch also failed for sort.q
[junit] 09/04/13 18:10:01 ERROR exec.ExecDriver: Job Submission failed with
exception 'java.io.IOExcep\
tion(Failed to get the current user's information.)'
[junit] java.io.IOException: Failed to get the current user's information.
[junit] at org.apache.hadoop.mapred.JobClient.getUGI(JobClient.java:717)
[junit] at
org.apache.hadoop.mapred.JobClient.configureCommandLineOptions(JobClient.java:592)
[junit] at
org.apache.hadoop.mapred.JobClient.submitJob(JobClient.java:774)
[junit] at
org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:393)
[junit] at
org.apache.hadoop.hive.ql.exec.ExecDriver.main(ExecDriver.java:556)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:597)
[junit] at org.apache.hadoop.util.RunJar.main(RunJar.java:165)
[junit] at org.apache.hadoop.mapred.JobShell.run(JobShell.java:54)
[junit] at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
[junit] at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:79)
[junit] at org.apache.hadoop.mapred.JobShell.main(JobShell.java:68)
[junit] Caused by: javax.security.auth.login.LoginException: Login failed:
whoami: cannot find usernam\
e for UID 1688
I dont think this has anything to do with your patch, but will run the tests
again and see
> Nested UDFs cause _very_ high memory usage when processing query
> ----------------------------------------------------------------
>
> Key: HIVE-372
> URL: https://issues.apache.org/jira/browse/HIVE-372
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Environment: Fedora Linux, 10x Amazon EC2 (Large Instance w/ 8GB Ram)
> Reporter: Steve Corona
> Attachments: HIVE-372.1.patch, HIVE-372.2.patch
>
>
> When nesting UDFs, the Hive Query processor takes a large amount of
> time+memory to process the query. For example, I ran something along the
> lines of:
> select trim( trim( trim(trim( trim( trim( trim( trim( trim(column)))))))))
> from test_table;
> This query needs 10GB+ of memory to process before it'll launch the job. The
> amount of memory increases exponentially with each nested UDF.
> Obviously, I am using trim() in this case as a simple example that causes the
> same problem to occur. In my actual use-case I had a bunch of nested
> regexp_replaces.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
