[
https://issues.apache.org/jira/browse/MAHOUT-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095857#comment-13095857
]
Sean Owen commented on MAHOUT-799:
----------------------------------
I'm also confused, reading this. SequenceFilesFromCsvFilter works when run as a
command-line program. But when used this way it never adds its options to the
command line and can't work. Was this the intent of the design? seems like
there needs to be additional cross-wiring for these filters to participate in
the command line.
> Cannot run SequenceFilesFromCsvFilter, ever
> -------------------------------------------
>
> Key: MAHOUT-799
> URL: https://issues.apache.org/jira/browse/MAHOUT-799
> Project: Mahout
> Issue Type: Bug
> Components: Examples
> Affects Versions: 0.5, 0.6
> Reporter: Jack Tanner
>
> As described here:
> http://mail-archives.apache.org/mod_mbox/mahout-user/201106.mbox/%[email protected]%3E
> SequenceFilesFromCsvFilter cannot be invoked with default parameter values,
> because it dies like so:
> bin/mahout seqdirectory -i input -o output -filter
> org.apache.mahout.text.SequenceFilesFromCsvFilter
> ...
> Caused by: java.lang.NumberFormatException: null
> at java.lang.Integer.parseInt(Integer.java:417)
> at java.lang.Integer.parseInt(Integer.java:499)
> at
> org.apache.mahout.text.SequenceFilesFromCsvFilter.<init>(SequenceFilesFromCsvFilter.java:56)
> If one adds the parameters -kcol 0 -vcol 0 (or their long-form versions), it
> dies like so:
> Unexpected -kcol while processing Job-Specific Options
> Commenting out SequenceFilesFromCsvFilter:56 and
> SequenceFilesFromCsvFilter:57, like so, allows the run to proceed
> // this.keyColumn = Integer.parseInt(options.get(KEY_COLUMN_OPTION[0]));
> // this.valueColumn =
> Integer.parseInt(options.get(VALUE_COLUMN_OPTION[0]));
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
