Thanks Matouk.
Updating the hive-log4j.properties and hive-exec-log4j.properties and changing
the location of hive.log.dir does work.
But my question is if I am calling hive as below, Why it does not work in case
of MAPJOIN . I see that in case of Mapjoin it creates a different file which
This is on the wrong mailing list, hence the non-activity.
+user@hive
bcc:user@hadoop
Thanks
+Vinod
On Feb 23, 2014, at 10:16 PM, orahad bigdata oracle...@gmail.com wrote:
Can somebody help me please?
Thanks
On Sun, Feb 23, 2014 at 3:27 AM, orahad bigdata oracle...@gmail.com wrote:
Hi Bryan
Yes. This is a known issue. Hive-5950
(https://issues.apache.org/jira/browse/HIVE-5950) will address it. It will soon
be committed to trunk.
Thanks
Prasanth Jayachandran
On Feb 24, 2014, at 11:21 AM, Bryan Jeffrey bryan.jeff...@gmail.com wrote:
All,
I am running Hadoop 2.2.0
I think TableDesc may not be using the right class loader here when it's trying
to get the class - other parts of the code specify the class loader to use but
in this context it does not. I've opened
https://issues.apache.org/jira/browse/HIVE-6495.
On Feb 23, 2014, at 4:05 AM, Andreas Koch
I'm assuming the jar was loaded using ADD JAR as opposed to the jar being on
the classpath?
On Feb 24, 2014, at 2:40 PM, Jason Dere jd...@hortonworks.com wrote:
I think TableDesc may not be using the right class loader here when it's
trying to get the class - other parts of the code specify
