You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Bhooshan Mogal (JIRA)" <ji...@apache.org> on 2013/10/24 01:57:42 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=13803570#comment-13803570 ]
Bhooshan Mogal commented on PIG-3441:
-------------------------------------
[~daijy] [~prkommireddi] any thoughts on this?
> 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_1.patch, PIG-3441.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.1#6144)