You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Luca Pireddu (Created) (JIRA)" <ji...@apache.org> on 2012/02/10 18:27:00 UTC
[jira] [Created] (HADOOP-8056) Configuration doesn't pass empty
string values to tasks
Configuration doesn't pass empty string values to tasks
-------------------------------------------------------
Key: HADOOP-8056
URL: https://issues.apache.org/jira/browse/HADOOP-8056
Project: Hadoop Common
Issue Type: Bug
Components: conf
Affects Versions: 1.0.0, 0.20.2
Reporter: Luca Pireddu
If I assign an *empty string* as a value to a property in a JobConf 'job' while I'm preparing it to run, the Configuration does store that value. I can retrieve it later while in the same process and the value is maintained.
However, if then call JobClient.runJob(job), the Configuration that is received by the Map and Reduce tasks doesn't contain the property, and calling JobConf.get with that property name returns null (instead of an empty string). Futher, if I inspect the job's configuration via Hadoop's web interface, the property isn't present.
It seems as if whatever serialization mechanism that is used to transmit the Configuration from the job client to the tasks discards properties with "" value.
--
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
[jira] [Commented] (HADOOP-8056) Configuration doesn't pass empty
string values to tasks
Posted by "Luca Pireddu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205573#comment-13205573 ]
Luca Pireddu commented on HADOOP-8056:
--------------------------------------
Hi Harsh,
I'd say it's a bug report as I feel the behaviour should be different. I think it would be reasonable to assume that the Configuration object in the tasks should appear identical what was present in the job client process.
> Configuration doesn't pass empty string values to tasks
> -------------------------------------------------------
>
> Key: HADOOP-8056
> URL: https://issues.apache.org/jira/browse/HADOOP-8056
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.20.2, 1.0.0
> Reporter: Luca Pireddu
>
> If I assign an *empty string* as a value to a property in a JobConf 'job' while I'm preparing it to run, the Configuration does store that value. I can retrieve it later while in the same process and the value is maintained.
> However, if then call JobClient.runJob(job), the Configuration that is received by the Map and Reduce tasks doesn't contain the property, and calling JobConf.get with that property name returns null (instead of an empty string). Futher, if I inspect the job's configuration via Hadoop's web interface, the property isn't present.
> It seems as if whatever serialization mechanism that is used to transmit the Configuration from the job client to the tasks discards properties with "" value.
--
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
[jira] [Commented] (HADOOP-8056) Configuration doesn't pass empty
string values to tasks
Posted by "Harsh J (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205564#comment-13205564 ]
Harsh J commented on HADOOP-8056:
---------------------------------
Luca,
Could you also tell us if this is a regression, or a bug report as you feel the behavior should be different?
> Configuration doesn't pass empty string values to tasks
> -------------------------------------------------------
>
> Key: HADOOP-8056
> URL: https://issues.apache.org/jira/browse/HADOOP-8056
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.20.2, 1.0.0
> Reporter: Luca Pireddu
>
> If I assign an *empty string* as a value to a property in a JobConf 'job' while I'm preparing it to run, the Configuration does store that value. I can retrieve it later while in the same process and the value is maintained.
> However, if then call JobClient.runJob(job), the Configuration that is received by the Map and Reduce tasks doesn't contain the property, and calling JobConf.get with that property name returns null (instead of an empty string). Futher, if I inspect the job's configuration via Hadoop's web interface, the property isn't present.
> It seems as if whatever serialization mechanism that is used to transmit the Configuration from the job client to the tasks discards properties with "" value.
--
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