Hi Nitin,
i reinstalled and did not modify anything, but it also can not work. It worked 
well when i first ran it months ago.

the output of locale command is below: 
LANG=zh_CN
LC_CTYPE="zh_CN"
LC_NUMERIC="zh_CN"
LC_TIME="zh_CN"
LC_COLLATE="zh_CN"
LC_MONETARY="zh_CN"
LC_MESSAGES="zh_CN"
LC_PAPER="zh_CN"
LC_NAME="zh_CN"
LC_ADDRESS="zh_CN"
LC_TELEPHONE="zh_CN"
LC_MEASUREMENT="zh_CN"
LC_IDENTIFICATION="zh_CN"
LC_ALL=

Thanks very much.




dianbo.zhu

From: Nitin Pawar
Date: 2012-05-22 18:42
To: user
Subject: Re: start hive cli error
error is due to default encoding.
hive supports UTF-8  based encoding but somehow your hive setup is picking up 
GB2312.


can you provide the output of locale command?


Thanks,
Nitin


On Tue, May 22, 2012 at 3:17 PM, Dimboo Zhu <[email protected]> wrote:

hi there,

I got the following trace stack when startuping hive cli. It worked=20 well 
last week when i just installed it.
Anybody can help? thanks,

Dianbau

[dzhu@bbdw-194 bin]$ ./hive
Logging initialized using configuration in j= 
ar:file:/local/dzhu/hadoop/hive-0.8.1-bin/lib/hive-common-0.8.1.jar!/hive-= 
log4j.properties
Hive history file=3D/tmp/dzhu/hive_job_log_dzhu_20120518130= 0_1495802688.txt
Exception in thread "main" java.io.UnsupportedEnc= odingException: GB2312
        at sun.nio.cs.St= 
reamEncoder.forOutputStreamWriter(StreamEncoder.java:42)
        at java.io.Outpu= tStreamWriter.<init>(OutputStreamWriter.java:83)
        at jline.Console= Reader.<init>(ConsoleReader.java:174)
        at org.apache.ha= doop.hive.cli.CliDriver.run(CliDriver.java:649)
        at org.apache.ha= doop.hive.cli.CliDriver.main(CliDriver.java:554)
        at sun.reflect.N= ativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.N= 
ativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.D= 
elegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
        at java.lang.ref= lect.Method.invoke(Method.java:597)
        at org.apache.ha= doop.util.RunJar.main(RunJar.java:156)





-- 
Nitin Pawar

Reply via email to