You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/04/05 12:52:17 UTC
[jira] [Commented] (MAHOUT-1501) ClusterOutputPostProcessorDriver
has private default constructor
[ https://issues.apache.org/jira/browse/MAHOUT-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961045#comment-13961045 ]
Hudson commented on MAHOUT-1501:
--------------------------------
SUCCESS: Integrated in Mahout-Quality #2554 (See [https://builds.apache.org/job/Mahout-Quality/2554/])
MAHOUT-1501 ClusterOutputPostProcessorDriver has private default constructor (ssc: rev 1585034)
* /mahout/trunk/CHANGELOG
* /mahout/trunk/core/src/main/java/org/apache/mahout/clustering/topdown/postprocessor/ClusterOutputPostProcessorDriver.java
> ClusterOutputPostProcessorDriver has private default constructor
> ----------------------------------------------------------------
>
> Key: MAHOUT-1501
> URL: https://issues.apache.org/jira/browse/MAHOUT-1501
> Project: Mahout
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 0.8
> Reporter: Reinis Vicups
> Assignee: Sebastian Schelter
> Priority: Trivial
>
> Some guy just decided to make default constructor of org.apache.mahout.clustering.topdown.postprocessor.ClusterOutputPostProcessorDriver private.
> This is not really bug, it's just inconsistent since all the other Drivers I found in mahout-core do not have private constructor.
> The private constructor inhibits me from doing this:
> {code}
> return ToolRunner.run(new ClusterOutputPostProcessorDriver(), clusterPPArgsStrings);
> {code}
> the very same way I am doing this:
> {code}
> return ToolRunner.run(new KMeansDriver(), kmeansArgsStrings);
> {code}
> Fix would be to just remove private constructor.
--
This message was sent by Atlassian JIRA
(v6.2#6252)