[ https://issues.apache.org/jira/browse/HADOOP-15357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424387#comment-16424387 ]
Jim Brennan commented on HADOOP-15357: -------------------------------------- Renamed local variable to fix the check-style issue and submitted a new patch. > Configuration.getPropsWithPrefix no longer does variable substitution > --------------------------------------------------------------------- > > Key: HADOOP-15357 > URL: https://issues.apache.org/jira/browse/HADOOP-15357 > Project: Hadoop Common > Issue Type: Bug > Reporter: Jim Brennan > Assignee: Jim Brennan > Priority: Major > Attachments: HADOOP-15357.001.patch, HADOOP-15357.002.patch > > > Before [HADOOP-13556], Configuration.getPropsWithPrefix() used the > Configuration.get() method to get the value of the variables. After > [HADOOP-13556], it now uses props.getProperty(). > The difference is that Configuration.get() does deprecation handling and more > importantly variable substitution on the value. So if a property has a > variable specified with ${variable_name}, it will no longer be expanded when > retrieved via getPropsWithPrefix(). > Was this change in behavior intentional? I am using this function in the fix > for [MAPREDUCE-7069], but we do want variable expansion to happen. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org