[
https://issues.apache.org/jira/browse/MAHOUT-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396189#comment-13396189
]
Andrew Look commented on MAHOUT-993:
------------------------------------
Has anyone picked this up? Looks like a good one to tackle for my first Mahout
patch.
Looking at the code, it's unclear which of these are supposed to have
arguments; I'm guessing that the following options do not accept arguments:
addOption("useKey", "u", "If the Key is a vector than dump that instead",
false);
addOption("printKey", "p", "Print out the key as well, delimited by tab (or
the value if useKey is true", false);
addOption("csv", "c", "Output the Vector as CSV. Otherwise it substitutes in
the terms for vector cell entries", false);
addOption("namesAsComments", "n", "If using CSV output, optionally add a
comment line for each NamedVector (if the vector is one) printing out the
name", false);
addOption("nameOnly", "N", "Use the name as the value for each NamedVector
(skip other vectors)", false);
addOption("sortVectors", "sort", "Sort output key/value pairs of the vector
entries in abs magnitude descending order", false);
addOption("quiet", "q", "Print only file contents", false);
addOption("sizeOnly", "sz", "Dump only the size of the vector", false);
Presumably, if these are all non-required options that do not take any
arguments, I can leverage AbstractJob.addFlag().
Does this sound right?
> Some vector dumper flags are expecting arguments.
> -------------------------------------------------
>
> Key: MAHOUT-993
> URL: https://issues.apache.org/jira/browse/MAHOUT-993
> Project: Mahout
> Issue Type: Bug
> Components: Integration
> Reporter: tom pierce
> Priority: Minor
> Fix For: 0.8
>
>
> I ran VectorDumper from the command line like this:
> $MAHOUT_HOME/bin/mahout vectordump -i ${HDFS_VECTS} --csv -p > ${LOCAL_VECTS}
> I've used this command before to dump similar vectors, but I'm now getting
> missing argument errors:
> ERROR common.AbstractJob: Missing value(s) --printKey
> You can add an argument after each of these flags to work around this problem
> for now:
> $MAHOUT_HOME/bin/mahout vectordump -i ${INPATH} --csv x -p x > ${LOCAL_OUT}
> I encountered this on the trunk, but I think it's likely this problem went
> out in 0.6; I can check in the next fews days if nobody does it first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
