Build failed in Jenkins: Mahout-Examples #11

See Changes: [srowen] And we do not seem to depend on jets3t anymore either, in fact it is excluded from the Hadoop dependency, so remove it [srowen] In spirit of MAHOUT-718, update Google Guava, and use its collections to repla

[jira] [Updated] (MAHOUT-721) Override org.apache.mahout.math.VectorWritable#toString()

[ https://issues.apache.org/jira/browse/MAHOUT-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daisuke Miyamoto updated MAHOUT-721: Attachment: VectorWritable.java.patch > Override org.apache.mahout.math.VectorWritable#toSt

[jira] [Created] (MAHOUT-721) Override org.apache.mahout.math.VectorWritable#toString()

Override org.apache.mahout.math.VectorWritable#toString() - Key: MAHOUT-721 URL: https://issues.apache.org/jira/browse/MAHOUT-721 Project: Mahout Issue Type: Improvement Compo

[jira] [Updated] (MAHOUT-721) Override org.apache.mahout.math.VectorWritable#toString()

[ https://issues.apache.org/jira/browse/MAHOUT-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daisuke Miyamoto updated MAHOUT-721: Status: Patch Available (was: Open) > Override org.apache.mahout.math.VectorWritable#toStr

Re: 0.6: off to the races!

I have also faced the problem in 598 I'll work in it. On Fri, Jun 3, 2011 at 4:42 PM, Lance Norskog wrote: > Congrats on the release! > > Do you consider 0.5 good enough that we don't have to keep saying "use > the trunk"? At least for some uses? > > Lance > > On Fri, Jun 3, 2011 at 8:51 AM, Hec

Re: 0.6: off to the races!

Congrats on the release! Do you consider 0.5 good enough that we don't have to keep saying "use the trunk"? At least for some uses? Lance On Fri, Jun 3, 2011 at 8:51 AM, Hector Yee wrote: > These are all complete with unit tests and are ready to go: > > Implement Boosting

[jira] [Updated] (MAHOUT-708) Update to Hadoop 0.20.203.0

[ https://issues.apache.org/jira/browse/MAHOUT-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated MAHOUT-708: - Description: I suggest we should move to Hadoop 0.20.203.0 for the next release. (Not 0.21 or furt

[jira] [Reopened] (MAHOUT-718) Small refactoring to broaden the use of Google Guava

[ https://issues.apache.org/jira/browse/MAHOUT-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Schelter reopened MAHOUT-718: --- will continue to refactor all code closing streams, files, etc > Small refactoring to br

[jira] [Commented] (MAHOUT-609) Add an option to make RecommenderJob write out it's computed item similarities

[ https://issues.apache.org/jira/browse/MAHOUT-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044020#comment-13044020 ] Sebastian Schelter commented on MAHOUT-609: --- I lost track of this but I'll defin

[jira] [Commented] (MAHOUT-537) Bring DistributedRowMatrix into compliance with Hadoop 0.20.2

[ https://issues.apache.org/jira/browse/MAHOUT-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044018#comment-13044018 ] Sean Owen commented on MAHOUT-537: -- The people have spoken! Forget 0.21. At best I think

[jira] [Commented] (MAHOUT-537) Bring DistributedRowMatrix into compliance with Hadoop 0.20.2

[ https://issues.apache.org/jira/browse/MAHOUT-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044015#comment-13044015 ] Dmitriy Lyubimov commented on MAHOUT-537: - bq. Does 0.21 bring back map-side joins

[jira] [Issue Comment Edited] (MAHOUT-537) Bring DistributedRowMatrix into compliance with Hadoop 0.20.2

[ https://issues.apache.org/jira/browse/MAHOUT-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044010#comment-13044010 ] Dmitriy Lyubimov edited comment on MAHOUT-537 at 6/3/11 8:14 PM: ---

[jira] [Commented] (MAHOUT-537) Bring DistributedRowMatrix into compliance with Hadoop 0.20.2

[ https://issues.apache.org/jira/browse/MAHOUT-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044010#comment-13044010 ] Dmitriy Lyubimov commented on MAHOUT-537: - Second Jake. -1 on this yet. (if i can

[jira] [Commented] (MAHOUT-716) Implement Boosting

[ https://issues.apache.org/jira/browse/MAHOUT-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043986#comment-13043986 ] Hector Yee commented on MAHOUT-716: --- Any feedback on this? I am planning to build more s

[jira] [Commented] (MAHOUT-597) Kernels in Mean Shift

[ https://issues.apache.org/jira/browse/MAHOUT-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043566#comment-13043566 ] Jeff Eastman commented on MAHOUT-597: - Should have committed it earlier. It has a few

Re: 0.6: off to the races!

These are all complete with unit tests and are ready to go: Implement Boosting Implement Gradient machine Implement Online Passive Aggressive learner< https://issues.apache.org/jira/browse/MAHOUT-7

Re: 0.6: off to the races!

537 and 524/712 here, along with any others I can help with. On Fri, Jun 3, 2011 at 11:37 AM, Dhruv Kumar wrote: > Actively working on this and should be ready for 0.6: > > Baum-Welch Algorithm on Map-Reduce for Parallel Hidden Markov Model > Training.

Re: 0.6: off to the races!

Actively working on this and should be ready for 0.6: Baum-Welch Algorithm on Map-Reduce for Parallel Hidden Markov Model Training. On Fri, Jun 3, 2011 at 5:20 AM, Sean Owen wrote: > 0.5 is out the door, and we already have 40 issues tagged f

[jira] [Commented] (MAHOUT-718) Small refactoring to broaden the use of Google Guava

[ https://issues.apache.org/jira/browse/MAHOUT-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043347#comment-13043347 ] Sebastian Schelter commented on MAHOUT-718: --- You're right, we should try to repl

0.6: off to the races!

0.5 is out the door, and we already have 40 issues tagged for 0.6 -- quite a bit of work to do! I see Sebastian and I are already cracking through several of them. Committer activity is still not quite keeping up with the backlog. It's an important time, and a time for those who can move issues to