[jira] [Assigned] (MAHOUT-1125) DatasetSplitter.run doesn't parseArguments before getOption so throws and exception always

["Sebastian Schelter (JIRA)" <ji...@apache.org>]

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

Sebastian Schelter reassigned MAHOUT-1125:
------------------------------------------

    Assignee: Sebastian Schelter  (was: Sean Owen)
    
> DatasetSplitter.run doesn't parseArguments before getOption so throws and exception always
> ------------------------------------------------------------------------------------------
>
>                 Key: MAHOUT-1125
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-1125
>             Project: Mahout
>          Issue Type: Bug
>          Components: Collaborative Filtering
>    Affects Versions: 0.8
>         Environment: all
>            Reporter: Pat Ferrel
>            Assignee: Sebastian Schelter
>            Priority: Blocker
>              Labels: patch
>             Fix For: 0.8
>
>         Attachments: MAHOUT-1125.1
>
>
> In DatasetSplitter.run it looks like getOption is being called before the parseArguments. When I do this 
> Map<String,List<String>> parsedArgs = parseArguments(args);
> if (parsedArgs == null) {
>  return -1;
> }
> before any call to getOption in DatasetSplitter.run it completes correctly. Not exactly sure how this is supposed to be done, it doesn't look like the options get parsed in the super class automatically.
> This will cause any invocation of splitDataset or DatasetSplitter to crash running the current trunk. 
> On Dec 5, 2012, at 1:58 PM, Pat Ferrel <pa...@gmail.com> wrote:
> does anyone know if mahout/examples/bin/factorize-movielens-1M.sh is still working? CLI version of splitDataset is crashing in my build (latest trunk). Even as in "mahout splitDataset" to get the params. Wouldn't be the first time I mucked up a build though.

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