You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Mona Chitnis (JIRA)" <ji...@apache.org> on 2014/06/24 21:24:25 UTC
[jira] [Commented] (PIG-3441) Allow Pig to use default resources
from Configuration objects
[ https://issues.apache.org/jira/browse/PIG-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042561#comment-14042561 ]
Mona Chitnis commented on PIG-3441:
-----------------------------------
I see TezLauncher is using the boolean {{loadDefaults}} as true. So we can apply same thing in MapReduceLauncher in addition to Daniel's comment about HExecutionEngine:111
{code}
@Override
public PigStats launchPig(PhysicalPlan php, String grpName, PigContext pc) throws Exception {
aggregateWarning = Boolean.parseBoolean(pc.getProperties().getProperty("aggregate.warning", "false"));
Configuration conf = ConfigurationUtil.toConfiguration(pc.getProperties(), true);
{code}
> Allow Pig to use default resources from Configuration objects
> -------------------------------------------------------------
>
> Key: PIG-3441
> URL: https://issues.apache.org/jira/browse/PIG-3441
> Project: Pig
> Issue Type: Bug
> Components: impl
> Affects Versions: 0.11.1
> Reporter: Bhooshan Mogal
> Attachments: PIG-3441.patch, PIG-3441_1.patch
>
>
> Pig currently ignores parameters from configuration files added statically to Configuration objects as Configuration.addDefaultResource(filename.xml).
> Consider the following scenario -
> In a hadoop FileSystem driver for a non-HDFS filesystem you load properties specific to that FileSystem in a static initializer block in the class that extends org.apache.hadoop.fs.Filesystem for your FileSystem like below -
> {code}
> class MyFileSystem extends FileSystem {
> static {
> Configuration.addDefaultResource("myfs-default.xml");
> Configuration.addDefaultResource("myfs-site.xml");
> }
> }
> {code}
> Interfaces like the Hadoop CLI, Hive, Hadoop M/R can find configuration parameters defined in these configuration files as long as they are on the classpath.
> However, Pig cannot find parameters from these files, because it ignores configuration files added statically.
> Pig should allow users to specify if they would like pig to read parameters from resources loaded statically.
--
This message was sent by Atlassian JIRA
(v6.2#6252)