hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lohit vijayarenu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1952) Streaming does not handle invalid -inputformat (typo by users for example)
Date Wed, 31 Oct 2007 00:11:50 GMT

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

lohit vijayarenu updated HADOOP-1952:
-------------------------------------

    Attachment: HADOOP-1952-2.patch

On the other hand if I think about it, should we log at info level inside goodClassOrNull
? If the mapper is 'cat' which is valid executable, we should not log saying cat class not
found, no? I reverting back the loggin inside goodClassOrNull and handle the failures in StreamJob
where needed. Thoughts? (Attached is a patch, which reverts only login changes)

> Streaming does not handle invalid -inputformat  (typo by users for example)
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-1952
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1952
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/streaming
>    Affects Versions: 0.14.1
>            Reporter: lohit vijayarenu
>            Assignee: lohit vijayarenu
>            Priority: Minor
>             Fix For: 0.16.0
>
>         Attachments: CatchInvalidInputFormat.patch, HADOOP-1952-1.patch, HADOOP-1952-2.patch
>
>
> Hadoop Streaming does not handle invalid inputformat class. For example -inputformat
INVALID class would not be thrown as an error. Instead it defaults to StreamInputFormat. If
an invalid inputformat is specified, it is good to fail. 

-- 
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