[jira] [Updated] (HAMA-749) Build for C++ Pipes
[ https://issues.apache.org/jira/browse/HAMA-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward J. Yoon updated HAMA-749: Fix Version/s: (was: 0.6.3) Build for C++ Pipes --- Key: HAMA-749 URL: https://issues.apache.org/jira/browse/HAMA-749 Project: Hama Issue Type: Improvement Components: build Reporter: Edward J. Yoon As described here - https://wiki.apache.org/hama/HamaPipes, currently it requires manual compile. The simple solution to create binary release, is use of ant-plugin. + In the future, Pipes project should be mavenized. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HAMA-612) BSP-based online collaborative filtering algorithm
[ https://issues.apache.org/jira/browse/HAMA-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward J. Yoon updated HAMA-612: Fix Version/s: (was: 0.6.3) BSP-based online collaborative filtering algorithm -- Key: HAMA-612 URL: https://issues.apache.org/jira/browse/HAMA-612 Project: Hama Issue Type: New Feature Components: machine learning Reporter: Edward J. Yoon Assignee: Ikhtiyor Ahmedov Labels: gsoc, gsoc2013, mentor Attachments: data_gen.py, HAMA-612_0.1.patch, ratings5K.dat I've finished implementation of online CF filtering algorithm, applied to real world application and evaluated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HAMA-774) CompositeInputFormat in Hama
[
https://issues.apache.org/jira/browse/HAMA-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward J. Yoon updated HAMA-774:
Fix Version/s: (was: 0.6.3)
CompositeInputFormat in Hama
Key: HAMA-774
URL: https://issues.apache.org/jira/browse/HAMA-774
Project: Hama
Issue Type: New Feature
Components: bsp core
Affects Versions: 0.6.2
Reporter: Martin Illecker
Assignee: Martin Illecker
Priority: Minor
Attachments: HAMA-774.patch
*Adapting Hadoop CompositeInputFormat to Hama.*
Adapt the CompositeInputFormat from Hadoop and integrate it into Hama.
e.g., Useful for matrix multiplication example by doing a inner join of two
matrices.
Therefore the Hadoop join package has been adapted within
*org.apache.hama.bsp.join*.
Finally I would need some help to integrate the CompositeInputFormat into
Hama by using
{code}
job.setInputFormat(CompositeInputFormat.class);
job.set(bsp.join.expr, CompositeInputFormat.compose(inner,
SequenceFileInputFormat.class, aPath, bPath));
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HAMA-790) Create a unit test for the SemiClustering example
[ https://issues.apache.org/jira/browse/HAMA-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward J. Yoon updated HAMA-790: Fix Version/s: (was: 0.6.3) Create a unit test for the SemiClustering example - Key: HAMA-790 URL: https://issues.apache.org/jira/browse/HAMA-790 Project: Hama Issue Type: Sub-task Components: graph, test Reporter: Edward J. Yoon Assignee: Renil J Please create a unit test for the SemiClustering example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HAMA-797) Reorganize core module by separating classes in bsp package to different folders.
[ https://issues.apache.org/jira/browse/HAMA-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ChiaHung Lin resolved HAMA-797. --- Resolution: Duplicate This is duplicate as https://issues.apache.org/jira/browse/HAMA-727. So close this ticket. Reorganize core module by separating classes in bsp package to different folders. - Key: HAMA-797 URL: https://issues.apache.org/jira/browse/HAMA-797 Project: Hama Issue Type: Improvement Reporter: ChiaHung Lin At the moment many classes such as Reader, Writer, Partitioner, etc all go to bsp package. Different classes should be organized with corresponded purposes such as io, conf, etc. so that the usage would be clearer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Skip minor release, and prepare 1.0
+0 Personally I would not go for 1.0 now though the release for 1.0 is ok for me. My reason is people may expect functions such as FT to be ready when it's in the version 1.0. Also it might be inevitably that people would compare MRv2, Giraph to Hama; and would think that MRv2, and Giraph would be more better/ stable than Hama because of FT, etc. regardless of differences between projects. On 17 August 2013 16:33, Edward J. Yoon edwardy...@apache.org wrote: Hi all, I was planning to cut a 0.6.3 release candidate (Hadoop 2.0 compatible version), however it seems the age of compete for the preoccupancy is past. So we don't need to hurry up now. Moreover, we are currently adding a lot of changes, and still need to be improved a lot. We knows what we should do exactly. Do you think we can skip minor release and prepare 1.0 now? -- Best Regards, Edward J. Yoon @eddieyoon
Re: [VOTE] Skip minor release, and prepare 1.0
I mean, put all TODO things into 1.0 roadmap, and just skip release until reach version 1.0. people would compare MRv2, Giraph to Hama; and would think that MRv2, and Giraph would be more better/ stable than Hama because of FT, etc. Spark also supports full fault-tolerance, and comparison has been already started.. Spark shows good performance, giraph shows good scalability. Hama has good performance and very flexible interface, but we are in gray zone. +0 I'm -0. I think we have to cut periodically. On Sun, Aug 18, 2013 at 4:26 PM, Chia-Hung Lin cli...@googlemail.com wrote: +0 Personally I would not go for 1.0 now though the release for 1.0 is ok for me. My reason is people may expect functions such as FT to be ready when it's in the version 1.0. Also it might be inevitably that people would compare MRv2, Giraph to Hama; and would think that MRv2, and Giraph would be more better/ stable than Hama because of FT, etc. regardless of differences between projects. On 17 August 2013 16:33, Edward J. Yoon edwardy...@apache.org wrote: Hi all, I was planning to cut a 0.6.3 release candidate (Hadoop 2.0 compatible version), however it seems the age of compete for the preoccupancy is past. So we don't need to hurry up now. Moreover, we are currently adding a lot of changes, and still need to be improved a lot. We knows what we should do exactly. Do you think we can skip minor release and prepare 1.0 now? -- Best Regards, Edward J. Yoon @eddieyoon -- Best Regards, Edward J. Yoon @eddieyoon
