hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-7271) Standardize error messages
Date Tue, 10 May 2011 18:13:47 GMT

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

Daryn Sharp updated HADOOP-7271:

    Attachment: HADOOP-7271.patch

Create path exceptions that encapsulate and enforce a standard posix/unix error message.

Change cmds, both redesigned and pending redesign, to use the new exceptions.  The changes
made to the pending cmds are to facilitate a redesign of multiple commands w/o constantly
breaking hdfs tests each time a command is updated.

Took out some of the TODO items related to standardizing.

> Standardize error messages
> --------------------------
>                 Key: HADOOP-7271
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7271
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 0.23.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>         Attachments: HADOOP-7271.patch
> The FsShell commands have no standard format for the same error message.  For instance,
here is a snippet of the variations of just one of many error messages:
> cmd: $path: No such file or directory
> cmd: cannot stat `$path': No such file or directory
> cmd: Can not find listing for $path
> cmd: Cannot access $path: No such file or directory.
> cmd: No such file or directory `$path'
> cmd: File does not exist: $path
> cmd: File $path does not exist
> ... etc ...
> These need to be common.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message