You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/03/25 04:21:52 UTC

[jira] [Commented] (MAHOUT-1639) streamingkmeans doesn't properly validate estimatedNumMapClusters -km

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

ASF GitHub Bot commented on MAHOUT-1639:
----------------------------------------

GitHub user smarthi opened a pull request:

    https://github.com/apache/mahout/pull/79

    MAHOUT-1639: streamingkmeans doesn't properly validate estimatedNumMapClusters -km

    Fixes MAHOUT-1639

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/smarthi/mahout Mahout-1639

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/mahout/pull/79.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #79
    
----
commit dc8805c85967787589796cae7ec45e98f7f4b5a9
Author: Suneel Marthi <su...@gmail.com>
Date:   2015-03-25T03:20:17Z

    MAHOUT-1639: streamingkmeans doesn't properly validate estimatedNumMapClusters -km

----


> streamingkmeans doesn't properly validate estimatedNumMapClusters -km
> ---------------------------------------------------------------------
>
>                 Key: MAHOUT-1639
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-1639
>             Project: Mahout
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 0.9
>            Reporter: Peter Sergeant
>            Assignee: Suneel Marthi
>            Priority: Minor
>              Labels: legacy
>             Fix For: 0.10.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The value of -km isn't checked by the CLI, which means if you don't specify it, you get the rather cryptic:
> {noformat}
> Exception in thread "main" java.lang.NumberFormatException: null
> 	at java.lang.Integer.parseInt(Integer.java:454)
> 	at java.lang.Integer.parseInt(Integer.java:527)
> 	at org.apache.mahout.clustering.streaming.mapreduce.StreamingKMeansDriver.configureOptionsForWorkers(StreamingKMeansDriver.java:252)
> 	at org.apache.mahout.clustering.streaming.mapreduce.StreamingKMeansDriver.run(StreamingKMeansDriver.java:239)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:79)
> 	at org.apache.mahout.clustering.streaming.mapreduce.StreamingKMeansDriver.main(StreamingKMeansDriver.java:491)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:68)
> 	at org.apache.hadoop.util.ProgramDriver.driver(ProgramDriver.java:139)
> 	at org.apache.mahout.driver.MahoutDriver.main(MahoutDriver.java:195)
> {noformat}
> Other parameters give helpful error messages when required



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)