hadoop-common-issues mailing list archives

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

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

Kengo Seki commented on HADOOP-7947:
------------------------------------

I have another idea. We add a new constructor like 'public GenericOptionsParser(String[] args,
boolean flag)' so as to utilize GenericOptionsParser, and make it avoid calling  processGeneralOptions()
in parseGeneralOptions() if the second argument is false. But I'm not sure this idea is good
or bad...

> 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
(v6.3.4#6332)

Mime
View raw message