Same for me. It's been there always, didn't really bother, however if
there's a fix, we should fix it.

Best regards,

Robin Verlangen
*Software engineer*
*
*
W http://www.robinverlangen.nl
E ro...@us2.nl

Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the intended recipient, you are reminded that
the information remains the property of the sender. You must not use,
disclose, distribute, copy, print or rely on this e-mail. If you have
received this message in error, please contact the sender immediately and
irrevocably delete this message and any copies.



2012/9/17 Connell, Chuck <chuck.conn...@nuance.com>

> I get the same warning. Could you please be more specific about "set the
> class path wrt log4J property file"? Exactly what should we do?
>
> Chuck Connell
> Nuance R&D Data Team
> Burlington, MA
>
>
> -----Original Message-----
> From: ashok.sa...@wipro.com [mailto:ashok.sa...@wipro.com]
> Sent: Monday, September 17, 2012 7:50 AM
> To: user@hive.apache.org
> Subject: RE: warning message while connecting Hive shell
>
> Please set the class path wrt log4J property file
>
> Thanks
> Ashok S.
>
>
> ________________________________________
> From: Ajit Kumar Shreevastava [ajit.shreevast...@hcl.com]
> Sent: Monday, September 17, 2012 4:11 PM
> To: user@hive.apache.org
> Subject: warning message while connecting Hive shell
>
> Hello ,
> When I want to make connection with hive  I got the following warning
> message.
>
> [hadoop@NHCLT-PC44-2 conf]$ hive
> WARNING: org.apache.hadoop.metrics.jvm.EventCounter is deprecated. Please
> use org.apache.hadoop.log.metrics.EventCounter in all the log4j.properties
> files.
> Logging initialized using configuration in
> jar:file:/home/hadoop/hive-0.8.1/lib/hive-common-0.8.1.jar!/hive-log4j.properties
> Hive history
> file=/tmp/hadoop/hive_job_log_hadoop_201209171607_883156857.txt
> hive> show tables;
> OK
> Time taken: 3.871 seconds
> hive>
>
> Does anyone have some clue regarding the warning message.
>
>
>

Reply via email to