[ https://issues.apache.org/jira/browse/PIG-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043690#comment-14043690 ]
Bhooshan Mogal commented on PIG-3441: ------------------------------------- [~chitnis], thanks for looking into this issue. If [~daijy] also agrees that these are the only 3 places that need to be changed, I can submit an updated patch. The initial patch allows users to configure this behavior based on a property, do you think it is necessary to make this configurable or should we set {{loadDefaults}} to {{true}} always? > 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)