[
https://issues.apache.org/jira/browse/HADOOP-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642508#action_12642508
]
Chris Douglas commented on HADOOP-4212:
---------------------------------------
bq. User looks at the ./hadoop queue list and finds out there is a job queue A,
and does not notice the extra space which is hidden in output in console and in
web. And mentions in his jobconf to submit to job queue A, the system checks
for queue information in job sees that there is no queue called A(without space
i.e.) and submits the job to the default queue. Which is wrong.
bq. You might argue that as an implementer, I should do checking with trimming
the space, but then again this can cause bugs to due accidental
mis-configuration.
I don't follow. Configuration should call trim before returning the queue name,
but if the callee(s) were to call trim on the same String, it "can cause bugs
[due to] accidental misconfiguration?"
> New lines and leading spaces are not trimmed of a value when configuration is
> read
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-4212
> URL: https://issues.apache.org/jira/browse/HADOOP-4212
> Project: Hadoop Core
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.18.1
> Environment: Generic
> Reporter: Sreekanth Ramakrishnan
> Assignee: Sreekanth Ramakrishnan
> Priority: Minor
> Attachments: HADOOP-4212-1.patch, HADOOP-4212-TESTCASE.patch
>
>
> While configuration value is read the leading and trailing spaces and new
> line characters are taken into account.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
