[ 
https://issues.apache.org/jira/browse/HIVE-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Laurel Hale reassigned HIVE-16735:
----------------------------------


> Please add that hive.mapred.local.mem must be set in MBs in the documentation
> -----------------------------------------------------------------------------
>
>                 Key: HIVE-16735
>                 URL: https://issues.apache.org/jira/browse/HIVE-16735
>             Project: Hive
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Laurel Hale
>            Assignee: Lefty Leverenz
>            Priority: Minor
>
> Hi Lefty,
> One of my developers noticed this and we do not document the local mode. 
> Thought I'd let you know.
> Here's a good place where you could put this:
> https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-QueryandDDLExecution
> There's already a small subsection where hive.mapred.local.mem is documented, 
> but there isn't any information about how to set the value. My developer 
> discovered that when you set it in bytes, it throws the following error:
> 2017-03-12 09:24:31,835 ERROR [HiveServer2-Background-Pool: Thread-22163()]: 
> mr.MapredLocalTask (MapredLocalTask.java:executeInChildVM(341)) - Exception: 
> java.lang.NumberFormatException: For input string: "4294967296"
> java.lang.NumberFormatException: For input string: "4294967296"
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:495)
> at java.lang.Integer.parseInt(Integer.java:527)
> at org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1259)
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:2415)
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:2424)
> at 
> org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask.executeInChildVM(MapredLocalTask.java:228)
> Instead, this value should be set in MBs for success.
> Thanks,
> Laurel



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to