[
https://issues.apache.org/jira/browse/HAMA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642033#action_12642033
]
Edward J. Yoon commented on HAMA-88:
------------------------------------
>> ...
>> in the second case, we don't use Matrix b again. we will delete the table in
>> HBase while we close the matrix.
>> ...
>> Matrix d = new DenseMatrix(conf, matrixname); // Matrix d will connect to
>> the table "MatrixC" in HBase. Use it again.
OK. 1, 2, 3 are good.
However, we may finally want to delete the matrices such as
HamaAdmin.delete(matrixname) or d.clear().... instead of close(). Right?
Please let me know am I wrong. : )
> DenseMatrix.close should not delete the table that are aliased in HamaAdmin.
> ----------------------------------------------------------------------------
>
> Key: HAMA-88
> URL: https://issues.apache.org/jira/browse/HAMA-88
> Project: Hama
> Issue Type: Bug
> Affects Versions: 0.1.0
> Reporter: Samuel Guo
> Fix For: 0.1.0
>
>
> for example:
> "
> String matrixname = "MatrixA";
> Matrix a = DenseMatrix.random(conf, 10, 10);
> a.save(matrixname);
> a.close();
> Matrix b = new DenseMatrix(conf, matrixname);
> "
> If we close a matrix, we alse delete the table in hbase. so we can use its
> aliase name keeped in HamaAdmin to reopen the matrix.
> so we need to identify if the matrix has been keeped in HamaAdmin. If the
> matrix has been aliased in HamaAdmin, we should not delete the table in
> Hbase.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
