hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3852) If ShellCommandExecutor had a toString() operator that listed the command run, its error messages may be more meaningful
Date Tue, 12 Aug 2008 21:59:44 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Owen O'Malley updated HADOOP-3852:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.19.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

I just committed this. Thanks, Steve!

> If ShellCommandExecutor had a toString() operator that listed the command run, its error
messages may be more meaningful
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3852
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3852
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 0.19.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>             Fix For: 0.19.0
>
>         Attachments: hadoop-3852.patch
>
>
> It may be easier to identify what causes error commands to be returned on an exec if
the command is included in the error message. this can be done with 
> * a toString() operator on the class that includes the list of arguments (when non null)
> * a test that this works with arguments with spaces, and a null array
> * relevant use of the operator when an execute fails, such as in TaskTracker

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message