[
https://issues.apache.org/jira/browse/HADOOP-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719960#action_12719960
]
Hemanth Yamijala commented on HADOOP-5913:
------------------------------------------
Rahul, the schedulingInfo member in Queue is an Object and not a string.
Therefore, it cannot be set to a default value like in JobQueueInfo. I verified
that if the object is null, it will not cause any damage elsewhere in code.
This seems to be a valid assumption. For instance, all calls to
Queue.getSchedulingInfo (except in test cases) check for null before using the
object. Does this make sense for you ?
> Allow administrators to be able to start and stop queues
> ---------------------------------------------------------
>
> Key: HADOOP-5913
> URL: https://issues.apache.org/jira/browse/HADOOP-5913
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Reporter: rahul k singh
> Assignee: rahul k singh
> Attachments: hadoop-5913-1.patch, hadoop-5913-10.patch,
> HADOOP-5913-11.patch, HADOOP-5913-12.patch, HADOOP-5913-13.patch,
> HADOOP-5913-14.patch, hadoop-5913-2.patch, hadoop-5913-3.patch,
> hadoop-5913-4.patch, hadoop-5913-5.patch, hadoop-5913-6.patch,
> hadoop-5913-7.patch, hadoop-5913-8.patch, hadoop-5913-9.patch
>
>
> This feature would provide functionality to stop and start queues in Hadoop
> at runtime.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
