[jira] Updated: (HAMA-88) DenseMatrix.close should not delete the table that are aliased in HamaAdmin.

["Samuel Guo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HAMA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Samuel Guo updated HAMA-88:
---------------------------

    Summary: DenseMatrix.close should not delete the table that are aliased in HamaAdmin.  (was: DenseMatrix.close should delete the table that are aliased in HamaAdmin.)

> 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.