You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2011/01/10 20:48:46 UTC
[jira] Created: (MAHOUT-580) Missing basePath in Bayes job /
InMemoryDataStore
Missing basePath in Bayes job / InMemoryDataStore
-------------------------------------------------
Key: MAHOUT-580
URL: https://issues.apache.org/jira/browse/MAHOUT-580
Project: Mahout
Issue Type: Bug
Components: Classification
Affects Versions: 0.4
Reporter: Sean Owen
Assignee: Robin Anil
Fix For: 0.5
Reported on user@ by Pierre Mage:
I found the following issue in the trunk: If the dataSource option is "hdfs"
in org.apache.mahout.classifier.
Classify, there is a problem with InMemoryBayesDatastore because its
basePath param is not defined :
To fix it, I edited Classify like this:
122. if ("hdfs".equals(dataSource)) {
123. params.set("basePath", modelBasePath);
Yes, looks like InMemoryDataStore expects this to be set -- so does HBaseDataStore. But that takes the base path (table) separately as a param. And InMemoryDataStore doesn't take it at all. I adjusted this since it seems correct. And then tried to centralized handling of Bayes params in BayesParameters since it seems to get half processed in this class only.
I have attached my own rather more elaborate patch that reflects this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAHOUT-580) Missing basePath in Bayes job /
InMemoryDataStore
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980397#action_12980397 ]
Hudson commented on MAHOUT-580:
-------------------------------
Integrated in Mahout-Quality #551 (See [https://hudson.apache.org/hudson/job/Mahout-Quality/551/])
MAHOUT-580
> Missing basePath in Bayes job / InMemoryDataStore
> -------------------------------------------------
>
> Key: MAHOUT-580
> URL: https://issues.apache.org/jira/browse/MAHOUT-580
> Project: Mahout
> Issue Type: Bug
> Components: Classification
> Affects Versions: 0.4
> Reporter: Sean Owen
> Assignee: Robin Anil
> Fix For: 0.5
>
> Attachments: MAHOUT-580.patch
>
>
> Reported on user@ by Pierre Mage:
> I found the following issue in the trunk: If the dataSource option is "hdfs"
> in org.apache.mahout.classifier.
> Classify, there is a problem with InMemoryBayesDatastore because its
> basePath param is not defined :
> To fix it, I edited Classify like this:
> 122. if ("hdfs".equals(dataSource)) {
> 123. params.set("basePath", modelBasePath);
> Yes, looks like InMemoryDataStore expects this to be set -- so does HBaseDataStore. But that takes the base path (table) separately as a param. And InMemoryDataStore doesn't take it at all. I adjusted this since it seems correct. And then tried to centralized handling of Bayes params in BayesParameters since it seems to get half processed in this class only.
> I have attached my own rather more elaborate patch that reflects this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MAHOUT-580) Missing basePath in Bayes job /
InMemoryDataStore
Posted by "Sean Owen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved MAHOUT-580.
------------------------------
Resolution: Fixed
> Missing basePath in Bayes job / InMemoryDataStore
> -------------------------------------------------
>
> Key: MAHOUT-580
> URL: https://issues.apache.org/jira/browse/MAHOUT-580
> Project: Mahout
> Issue Type: Bug
> Components: Classification
> Affects Versions: 0.4
> Reporter: Sean Owen
> Assignee: Robin Anil
> Fix For: 0.5
>
> Attachments: MAHOUT-580.patch
>
>
> Reported on user@ by Pierre Mage:
> I found the following issue in the trunk: If the dataSource option is "hdfs"
> in org.apache.mahout.classifier.
> Classify, there is a problem with InMemoryBayesDatastore because its
> basePath param is not defined :
> To fix it, I edited Classify like this:
> 122. if ("hdfs".equals(dataSource)) {
> 123. params.set("basePath", modelBasePath);
> Yes, looks like InMemoryDataStore expects this to be set -- so does HBaseDataStore. But that takes the base path (table) separately as a param. And InMemoryDataStore doesn't take it at all. I adjusted this since it seems correct. And then tried to centralized handling of Bayes params in BayesParameters since it seems to get half processed in this class only.
> I have attached my own rather more elaborate patch that reflects this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAHOUT-580) Missing basePath in Bayes job /
InMemoryDataStore
Posted by "Sean Owen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen updated MAHOUT-580:
-----------------------------
Attachment: MAHOUT-580.patch
> Missing basePath in Bayes job / InMemoryDataStore
> -------------------------------------------------
>
> Key: MAHOUT-580
> URL: https://issues.apache.org/jira/browse/MAHOUT-580
> Project: Mahout
> Issue Type: Bug
> Components: Classification
> Affects Versions: 0.4
> Reporter: Sean Owen
> Assignee: Robin Anil
> Fix For: 0.5
>
> Attachments: MAHOUT-580.patch
>
>
> Reported on user@ by Pierre Mage:
> I found the following issue in the trunk: If the dataSource option is "hdfs"
> in org.apache.mahout.classifier.
> Classify, there is a problem with InMemoryBayesDatastore because its
> basePath param is not defined :
> To fix it, I edited Classify like this:
> 122. if ("hdfs".equals(dataSource)) {
> 123. params.set("basePath", modelBasePath);
> Yes, looks like InMemoryDataStore expects this to be set -- so does HBaseDataStore. But that takes the base path (table) separately as a param. And InMemoryDataStore doesn't take it at all. I adjusted this since it seems correct. And then tried to centralized handling of Bayes params in BayesParameters since it seems to get half processed in this class only.
> I have attached my own rather more elaborate patch that reflects this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.