Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Pig >> mail # user >> Pig default properties/configuration


+
Jeff Yuan 2013-03-04, 16:28
Copy link to this message
-
Re: Pig default properties/configuration
Hi Jeff,

That's a side effect of that Pig has to support both Hadoop1.x and
Hadoop2.x, and Hadoop2.x depreciates a lot of old properties. One
workaround is upping the logging level of Hadoop Configuration as follows:

1. Edit conf/log4j.properties as follows:

log4j.logger.org.apache.hadoop.conf.Configuration=ERROR, A

2. Edit conf/pig.properties as follows:

# log4jconf log4j configuration file
log4jconf=<path_to_log4j.properties>/log4j.properties

Thanks,
Cheolsoo
On Mon, Mar 4, 2013 at 8:28 AM, Jeff Yuan <[EMAIL PROTECTED]> wrote:

> I'm calling Pig (with entry point from Main.java) from another Java
> program. When it runs, I get a ton of warnings like these:
>
> 13/03/03 15:38:55 WARN conf.Configuration: dfs.max.objects is
> deprecated. Instead, use dfs.namenode.max.objects
> 13/03/03 15:38:55 WARN conf.Configuration: mapred.task.id is
> deprecated. Instead, use mapreduce.task.attempt.id
>
> My question is, am I missing a step to load the default
> configuration/properties? Or does Pig always show a lot of these
> similar warnings? Any way to hide these during execution or to
> otherwise?
>
> Thanks.
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB