[ https://issues.apache.org/jira/browse/PIG-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122180#comment-14122180 ]
Bhooshan Mogal commented on PIG-3441: ------------------------------------- Apologies, please disregard my previous comment. I can still see the same issue even after applying this patch. I forgot that I had a workaround in my code to do a {{conf.addResource}} if {{Configuration.addDefaultResource}} does not work. After disabling that workaround, pig can still not find the default resources. I then tried removing the default 'false' passed to the {{Configuration}} constructor in {{ConfigurationUtil.toConfiguration}} and that seems to work again, like before. I'm still trying to understand the flow here, but its difficult because {{ConfigurationUtil.toConfiguration}} seems to be called multiple times for different reasons. > 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 > Assignee: Daniel Dai > Attachments: PIG-3441-2.patch, PIG-3441-3.patch, 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.3.4#6332)