>> May be I think that we need some tools to load matrices to HBase from other >> sources(files, database, ... ). >> These tools may stay at the Utils package.
Oh, I see. HamaAdmin will save the matrix : matrix1 -> hbase:table_name_for_matrix1 matrix2 -> hdfs:file_name_for_matrix2 Then, Let's add load/save/delete/... function to HamaAdmin from matrix implementation as describe below. I guess we also need to log a type (e.g. dense, sparse...) of matrix when it saved. Matrix a = HamaAdmin.load(matrix1); On Mon, Oct 13, 2008 at 10:00 AM, Samuel Guo (JIRA) <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/HAMA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638930#action_12638930 > ] > > Samuel Guo commented on HAMA-76: > -------------------------------- > > hmm. Using HamaAdmin to manage all the matrices in table is a good design. > May be I think that we need some tools to load matrices to HBase from other > sources(files, database, ... ). > These tools may stay at the Utils package. > > Any suggestion? > >> Remove load method. >> ------------------- >> >> Key: HAMA-76 >> URL: https://issues.apache.org/jira/browse/HAMA-76 >> Project: Hama >> Issue Type: Improvement >> Components: interface >> Reporter: Edward J. Yoon >> Assignee: Edward J. Yoon >> Priority: Minor >> Fix For: 0.1.0 >> >> Attachments: HAMA-76.patch >> >> >> We can use a constructor such as Matrix(conf, name) instead of load(). It'll >> be more simplified. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > -- Best regards, Edward J. Yoon [EMAIL PROTECTED] http://blog.udanax.org
