Hi Raj,
You can use "-l" option while starting up pig, or set "pig.logfile" either
in your script or pig.properties
pig -l foo.log myscript.pig
set pig.logfile foo.log -- within your script
pig.logfile=foo.log # within pig.properties
On Fri, May 31, 2013 at 6:47 AM, Raj Hadoop wrote:
Praveen,
Including those worked! Thanks.
But I have some questions:
1-Why do we even need to do this? If in a cluster, same nodes are being
used as DataNodes/TaskTrackers/RegionServers then shouldn't these libs be
on the classpath already? These are pretty basic libs? Had it been the case
that w
Hi,
How do I modify the error messages file location in Pig.
Is there any property in "pig.properties" or "log4j.properties".
Thanks,
Raj
export HBASE_CLASS= jarfiles
export HADOOP_CLASS= jarfiles
*Thanks & Regards*
∞
Shashwat Shriparv
On Fri, May 31, 2013 at 4:49 PM, Shahab Yunus wrote:
> Thanks, I will try and provide an update. Out of curiosity, did you ever
> resolved it?
>
> Regards,
> Shahab
>
>
> On Fri, May 31, 2013
Thanks, I will try and provide an update. Out of curiosity, did you ever
resolved it?
Regards,
Shahab
On Fri, May 31, 2013 at 4:17 AM, Praveen Bysani wrote:
> Yes, it could be. Try registering these jar files
>
> /opt/cloudera/parcels/CDH-/lib/hbase/hbase--security.jar
> /opt/cloudera/parcels/C
Yes, it could be. Try registering these jar files
/opt/cloudera/parcels/CDH-/lib/hbase/hbase--security.jar
/opt/cloudera/parcels/CDH-/lib/zookeeper/zookeeper-.jar
On 30 May 2013 20:14, Shahab Yunus wrote:
> I am not explicitly registering any of these jars in the script. The
> cluster was setup
