hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsuyoshi Ozawa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7947) Validate XMLs if a relevant tool is available, when using scripts
Date Sat, 14 Mar 2015 16:12:38 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361877#comment-14361877

Tsuyoshi Ozawa commented on HADOOP-7947:

[~sekikn] [~aw] thank you for taking this interesting work! IMHO, we shouldn't all work here.
It means we should add "conftest" command partially here. 

1. For now, I don't think we must support conftest --conf at first. It would be useful to
add only "bin/hadoop conftest" here.
2. Creating new JIRA and let's discuss and brush up conftest command there as Allen mentioned
- supporting --conf option there.

I think this is straightforward way. What do you think?

> Validate XMLs if a relevant tool is available, when using scripts
> -----------------------------------------------------------------
>                 Key: HADOOP-7947
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7947
>             Project: Hadoop Common
>          Issue Type: Wish
>          Components: scripts
>    Affects Versions: 2.7.0
>            Reporter: Harsh J
>            Assignee: Kengo Seki
>              Labels: newbie
>         Attachments: HADOOP-7947.001.patch, HADOOP-7947.002.patch, HADOOP-7947.003.patch
> Given that we are locked down to using only XML for configuration and most of the administrators
need to manage it by themselves (unless a tool that manages for you is used), it would be
good to also validate the provided config XML (*-site.xml) files with a tool like {{xmllint}}
or maybe Xerces somehow, when running a command or (at least) when starting up daemons.
> We should use this only if a relevant tool is available, and optionally be silent if
the env. requests.

This message was sent by Atlassian JIRA

View raw message