You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2013/07/25 16:41:49 UTC

[jira] [Updated] (MAHOUT-1291) MahoutDriver yields cosmetically suboptimal exception when bin/mahout runs without args, on some Hadoop versions

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

Sean Owen updated MAHOUT-1291:
------------------------------

    Attachment: MAHOUT-1291.patch
    
> MahoutDriver yields cosmetically suboptimal exception when bin/mahout runs without args, on some Hadoop versions
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: MAHOUT-1291
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-1291
>             Project: Mahout
>          Issue Type: Improvement
>    Affects Versions: 0.8
>            Reporter: Sean Owen
>            Priority: Trivial
>             Fix For: 0.9
>
>         Attachments: MAHOUT-1291.patch
>
>
> If you run bin/mahout without arguments, an error is correctly displayed about lack of an argument. The part that displays the error is actually within Hadoop code. In some versions of Hadoop, in the error case, it will quit the JVM with System.exit(). In others, it does not.
> In the calling code in MahoutDriver, in this error case, the main() method does not actually return. So, for versions where Hadoop code doesn't immediately exit the JVM, execution continues. This yields another exception. It's pretty harmless but ugly.
> Attached is a one-line fix, to return from main() in the error case, which is more correct to begin with.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira