[
https://issues.apache.org/jira/browse/MAHOUT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Anil resolved MAHOUT-285.
---
Resolution: Fixed
Committed. More or less working. Haven't tested against large dataset just to
make
[
https://issues.apache.org/jira/browse/MAHOUT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Anil reassigned MAHOUT-285:
-
Assignee: Robin Anil
> Wrap up collocation and dictionary vectorizer integration
> --
[
https://issues.apache.org/jira/browse/MAHOUT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Drew Farris updated MAHOUT-285:
---
Attachment: MAHOUT-285.patch
Robin got the bulk of this done yesterday night, reviewed his changes an
[
https://issues.apache.org/jira/browse/MAHOUT-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832380#action_12832380
]
Rohini Uppuluri commented on MAHOUT-153:
Hi all,
I have implemented an extension
Good catch, I will look at this more tonight but I am pretty certain
that you are correct. I will commit a fix soon if applicable.
On Wed, Feb 10, 2010 at 9:27 PM, Guohua Hao wrote:
> Hello All,
>
> When I studied the code on the trunk, I was wondering that on line 130 in
> the class org.apache.m
[
https://issues.apache.org/jira/browse/MAHOUT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832263#action_12832263
]
Robin Anil commented on MAHOUT-285:
---
Success. I just finished the integration of Dictiona
[
https://issues.apache.org/jira/browse/MAHOUT-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832239#action_12832239
]
Jake Mannix commented on MAHOUT-185:
Why don't we just commit the shell script and clos
Hello All,
When I studied the code on the trunk, I was wondering that on line 130 in
the class org.apache.mahout.cf.taste.hadoop.item.RecommenderMapper, shall we
use the condition
userVector.get(index) == 0.0
instead?
My understanding is that only the item which is not rated by the user (i.e.,
Applicable for tiny clusters only. There is no fault tolerance and all data
is streamed from map to reduce. There is also no distributed store (they
are depending on NFS or local data copies).
That is highly effective for algorithms like k-means on small clusters which
are I/O bound. Small clus
I actually want to try and see how much runs on Amazon EMR (0.18.3*), as
that would
be good to document. I like running on 0.20 better, and I certainly think
we should
recommend people use it, but there are certainly some jobs which simply
won't run
on 0.18, although it would be good to document w
Right.
On Wed, Feb 10, 2010 at 10:45 AM, Robin Anil wrote:
> On Thu, Feb 11, 2010 at 12:10 AM, Ted Dunning
> wrote:
>
> > The use of MapMaker should probably be updated to use the same object
> from
> > google collections (which is now in guava).
> >
> So without watchmaker making that change n
+1 from me even though I am still on 19 at work.
On Wed, Feb 10, 2010 at 3:53 AM, Isabel Drost wrote:
> On Wed Sean Owen wrote:
>
> > I'd say we recommend 0.20, since that's what we develop against and
> > it's the current stable release, and everything we have works on it.
> >
> > We can also
On Thu, Feb 11, 2010 at 12:10 AM, Ted Dunning wrote:
> The use of MapMaker should probably be updated to use the same object from
> google collections (which is now in guava).
>
So without watchmaker making that change nothing could be done right
>
> On Wed, Feb 10, 2010 at 9:27 AM, Robin Anil
The use of MapMaker should probably be updated to use the same object from
google collections (which is now in guava).
On Wed, Feb 10, 2010 at 9:27 AM, Robin Anil wrote:
> Kicked the two files out. We can always bring it back as its in the
> repository
>
>
>
> On Wed, Feb 10, 2010 at 10:56 PM, J
Well, Things seems to be heating up. We better start refactoring :)
Robin
-- Forwarded message --
From: Jaliya Ekanayake
Date: Wed, Feb 10, 2010 at 11:37 PM
Subject: Twister: Iterative MapReduce
To: common-...@hadoop.apache.org
Hi All,
We would like to announce the first op
[
https://issues.apache.org/jira/browse/MAHOUT-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832089#action_12832089
]
Ted Dunning commented on MAHOUT-227:
Zhao,
My thought is that having a good sequentia
Kicked the two files out. We can always bring it back as its in the
repository
On Wed, Feb 10, 2010 at 10:56 PM, Jeff Eastman
wrote:
> Robin Anil wrote:
>
>> any more +1s ?
>>
>>
>>
> +1 keep Mahout as unentangled as possible
>
Robin Anil wrote:
any more +1s ?
+1 keep Mahout as unentangled as possible
[
https://issues.apache.org/jira/browse/MAHOUT-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isabel Drost updated MAHOUT-281:
Status: Patch Available (was: Open)
> scm urls are wrong in the poms
> ---
[
https://issues.apache.org/jira/browse/MAHOUT-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isabel Drost updated MAHOUT-281:
Attachment: MAHOUT-281.diff
Changed scm connection strings. (Needed a comparably simple example to
We could have a profile for that.
On Wed, Feb 10, 2010 at 11:17 AM, Drew Farris wrote:
> On Wed, Feb 10, 2010 at 6:40 AM, Sean Owen wrote:
>>
>> We can also say it should work on 0.19 and 0.18, but we don't
>> guarantee or support that. (Slightly different than my last suggestion
>> -- we don't
[
https://issues.apache.org/jira/browse/MAHOUT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Drew Farris updated MAHOUT-285:
---
Attachment: MAHOUT-285.patch
Robin, check out the DocumentProcessor integration here, is this what yo
[
https://issues.apache.org/jira/browse/MAHOUT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832047#action_12832047
]
Drew Farris commented on MAHOUT-285:
Yes, I'm very close on this and should be able to
On Wed, Feb 10, 2010 at 6:40 AM, Sean Owen wrote:
>
> We can also say it should work on 0.19 and 0.18, but we don't
> guarantee or support that. (Slightly different than my last suggestion
> -- we don't actually know how it all goes on 0.19)
>
+1 -- we can't really know how it will work unless we
[
https://issues.apache.org/jira/browse/MAHOUT-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832022#action_12832022
]
zhao zhendong commented on MAHOUT-232:
--
Hi Sean,
For Mahout-232, I suppose to finishe
[
https://issues.apache.org/jira/browse/MAHOUT-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831973#action_12831973
]
Sean Owen commented on MAHOUT-288:
--
It's up to your judgment about whether it's useful eno
[
https://issues.apache.org/jira/browse/MAHOUT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831964#action_12831964
]
Robin Anil commented on MAHOUT-285:
---
This wont take much time nor does it depend on anyth
[
https://issues.apache.org/jira/browse/MAHOUT-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831961#action_12831961
]
Robin Anil commented on MAHOUT-288:
---
Its a hacky solution for 0.3, just to get ARFF runni
On Wed Sean Owen wrote:
> I'd say we recommend 0.20, since that's what we develop against and
> it's the current stable release, and everything we have works on it.
>
> We can also say it should work on 0.19 and 0.18, but we don't
> guarantee or support that. (Slightly different than my last sug
[
https://issues.apache.org/jira/browse/MAHOUT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831958#action_12831958
]
Sean Owen commented on MAHOUT-285:
--
Do you guys think the current patch is commitable? or
[
https://issues.apache.org/jira/browse/MAHOUT-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated MAHOUT-232:
-
Fix Version/s: (was: 0.3)
0.4
This is evidently linked to MAHOUT-227 and so pushes
[
https://issues.apache.org/jira/browse/MAHOUT-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated MAHOUT-227:
-
Fix Version/s: (was: 0.3)
0.4
Moving to 0.4 per Zhao's comment
> Parallel SVM
> -
On Wed Jake Mannix wrote:
> > May I kick them out?
> >
>
> +1
+1 from me as well.
Isabel
[
https://issues.apache.org/jira/browse/MAHOUT-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated MAHOUT-288:
-
Fix Version/s: (was: 0.3)
0.4
For 0.4 right? we shouldn't be opening anything agai
[
https://issues.apache.org/jira/browse/MAHOUT-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated MAHOUT-185:
-
Fix Version/s: (was: 0.3)
0.4
This timed out for 0.3 methinks
> Add mahout shell
I'd say we recommend 0.20, since that's what we develop against and
it's the current stable release, and everything we have works on it.
We can also say it should work on 0.19 and 0.18, but we don't
guarantee or support that. (Slightly different than my last suggestion
-- we don't actually know ho
On Wed, 10 Feb 2010 11:10:41 +
Sean wrote:
> For simplicity, I'd document that Mahout works on 0.19 and 0.20, and
> may work on 0.18
+1
Assuming that the majority of the algorithms may work on e.g. 0.19, we
could tell users something along the lines of "works with Hadoop 0.19,
except $algor
fpm is purely based on 0.20.x api and works perfectly fine on that
On Wed, Feb 10, 2010 at 4:40 PM, Sean wrote:
> For simplicity, I'd document that Mahout works on 0.19 and 0.20, and
> may work on 0.18. That's more what people need to know, rather than
> confuse the issue with talk of old/new
For simplicity, I'd document that Mahout works on 0.19 and 0.20, and
may work on 0.18. That's more what people need to know, rather than
confuse the issue with talk of old/new APIs, since even I am confused
about what's going on. The two are blending together, while one is
deprecated, and it causes
On Thu deneche abdelhakim wrote:
> although I maintain two versions of Decision Forests, one with the old
> api and with the new one, the differences between the two APIs are so
> important that I can't just keep working on the two versions. Thus all
> the new stuff is being committed using the ne
Hi Mahouters
I am trying to find out how you are using Mahout for your work or
project, or which among the algorithms in Mahout are more important for you
to do that work. And finally what do you expect to see in Mahout(A kind of a
wish list). It wont take much of your time. Please reply with
[
https://issues.apache.org/jira/browse/MAHOUT-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831926#action_12831926
]
Shashikant Kore commented on MAHOUT-153:
Pallavi,
I can see two potential improvem
[
https://issues.apache.org/jira/browse/MAHOUT-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jake Mannix updated MAHOUT-180:
---
Attachment: MAHOUT-180.patch
Adds an EigenVerificationJob, which takes just as long as the
Distribut
Yes, I imagine lots of the code in there can be removed
On Wed, Feb 10, 2010 at 8:50 AM, Robin Anil wrote:
> any more +1s ?
>
Select only Binary attributes from ARFF format for Bayes Classifier
---
Key: MAHOUT-288
URL: https://issues.apache.org/jira/browse/MAHOUT-288
Project: Mahout
Issue Type: Sub-tas
[
https://issues.apache.org/jira/browse/MAHOUT-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831912#action_12831912
]
Robin Anil commented on MAHOUT-286:
---
I will have to move this to 0.4. Bayes classifier on
Bayes Classifier should use Vector as input
---
Key: MAHOUT-287
URL: https://issues.apache.org/jira/browse/MAHOUT-287
Project: Mahout
Issue Type: Improvement
Components: Classification
Af
[
https://issues.apache.org/jira/browse/MAHOUT-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Häger updated MAHOUT-286:
Attachment: run.sh
data.training.arff
data.arff
Attaching:
* data.
any more +1s ?
In case we need to do need multithread all the algos should be reusable in
that framework without any code modification. And I have a feeling hadoop
will strive to improve multicore processor utilisation.
Robin
On Wed, Feb 10, 2010 at 2:13 PM, Jake Mannix wrote:
> On Wed, Feb 10, 2010 at 12:39
On Wed, Feb 10, 2010 at 12:39 AM, Robin Anil wrote:
> Smp.java is not used anywhere.
> SmpBlas is used at one place and could be replaced by Sequential version.
> In
> Mahout we dont need to run multithreading anyways. Assuming our allegiance
> is to Hadoop M/R. and a map job shouldn't be doing f
Smp.java is not used anywhere.
SmpBlas is used at one place and could be replaced by Sequential version. In
Mahout we dont need to run multithreading anyways. Assuming our allegiance
is to Hadoop M/R. and a map job shouldn't be doing further spliting of work
May I kick them out?
Robin
On Wed, Fe
52 matches
Mail list logo
