[
https://issues.apache.org/jira/browse/HADOOP-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796018#action_12796018
]
Steve Loughran commented on HADOOP-6408:
----------------------------------------
Looks pretty good. If there is one change I'd do it is have an unrecognised
format generate an HTTP 400 response (bad request) when an unknown format is
hit; then add a test for this. That way automated clients asking for formats
get to fail without trying to parse the (presumably invalid) text
> Add a /conf servlet to dump running configuration
> -------------------------------------------------
>
> Key: HADOOP-6408
> URL: https://issues.apache.org/jira/browse/HADOOP-6408
> Project: Hadoop Common
> Issue Type: New Feature
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 0.22.0
>
> Attachments: hadoop-6408.txt, hadoop-6408.txt, hadoop-6408.txt,
> hadoop-6408.txt, hadoop-6408.txt, hadoop-6408.txt
>
>
> HADOOP-6184 added a command line flag to dump the running configuration. It
> would be great for cluster troubleshooting to provide access to this as a
> servlet, preferably in both JSON and XML formats. But really, any format
> would be better than nothing. This should/could go into all of the daemons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
