hive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 麦树荣 <shurong....@qunar.com>
Subject 答复: hive 0.11.0 startup
Date Mon, 13 Jan 2014 05:47:03 GMT
Hi,

Hive-0.11.0 can work with hadoop-2.2.0, check if your environment variables about hadoop such
as ‘HADOOP_HOME’ are right.

发件人: Kennedy, Sean C. [mailto:sean.kennedy@merck.com]
发送时间: 2014年1月11日 6:04
收件人: user@hive.apache.org
主题: hive 0.11.0 startup

When I start hive I get the following:


hduser@ip-54-40-31-118 bin]$ ./hive
debug  “ Make sure we are using a compatible version of hdfs”

14/01/10 17:00:22 INFO Configuration.deprecation: mapred.input.dir.recursive is deprecated.
Instead, use mapreduce.input.fileinputformat.input.dir.recursive
14/01/10 17:00:22 INFO Configuration.deprecation: mapred.max.split.size is deprecated. Instead,
use mapreduce.input.fileinputformat.split.maxsize

Hive Version:  hive-0.11.0.tar.gz
Hadoop Version:  2.2.0


Any help ?

Sincere Thanks in Advance

Sean


From: Kristopher Kane [mailto:kkane.list@gmail.com]
Sent: Friday, January 10, 2014 4:32 PM
To: user@hive.apache.org
Subject: ORC numberformatexcetion with type DECIMAL

Hive .12 on Hadoop 2

I have a table with a mix of STRING and DECIMAL fields that is stored as ORC no compression
or partitions.
I wanted to create a copy of this table with CTAS, stored also as ORC.
The job fails with NumberFormatException at the HiveDecimal class but I can't narrow it down
the the field.

The job succeeds if I store the new table with the default storage format.

A bit strange going from ORC to ORC with CTAS isn't it?

Thanks,

-Kris

Notice:  This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates Direct contact information
for affiliates is available at
http://www.merck.com/contact/contacts.html) that may be confidential,
proprietary copyrighted and/or legally privileged. It is intended solely
for the use of the individual or entity named on this message. If you are
not the intended recipient, and have received this message in error,
please notify us immediately by reply e-mail and then delete it from
your system.
Mime
View raw message