[
https://issues.apache.org/jira/browse/HCATALOG-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423126#comment-13423126
]
Travis Crawford commented on HCATALOG-449:
------------------------------------------
+1 will commit if tests pass.
I didn't understand this issue at first and learned the following.
{{Configuration}} values have some [variable expansion
rules|http://hadoop.apache.org/common/docs/current/api/org/apache/hadoop/conf/Configuration.html#VariableExpansion]
that are applied when you {{get}} a value. These rules are not applied when
treating the {{Configuration}} as a Map<String, String>, which is how one of
the values being compared is retrieved. {{getRaw}} allows one to retrieve the
unexpanded value which is needed here for comparison.
> HCatLoader is mistakenly identifying Configuration parameters to store
> ----------------------------------------------------------------------
>
> Key: HCATALOG-449
> URL: https://issues.apache.org/jira/browse/HCATALOG-449
> Project: HCatalog
> Issue Type: Bug
> Components: client, mapreduce
> Affects Versions: 0.4
> Reporter: Chris Drome
> Assignee: Chris Drome
> Fix For: 0.4
>
> Attachments: HCATALOG-449-trunk.patch, HCATALOG-449.patch
>
>
> HCatLoader.setLocation mistakenly compares expanded Configuration values with
> raw values when storing differences in Configurations.
> When running on Hadoop 23 any job which has a reduce step fails because it
> cannot locate the map data. This causes the reducer to fall into an endless
> loop until disk space is consumed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
