Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hama-dev@incubator.apache.org
Message-ID: <238081318.1225261004222.JavaMail.jira@brutus>
Date: Tue, 28 Oct 2008 23:16:44 -0700 (PDT)
From: "Samuel Guo (JIRA)" <jira@apache.org>
To: hama-dev@incubator.apache.org
Subject: [jira] Updated: (HAMA-88) DenseMatrix.close should not delete the
 table that are aliased in HamaAdmin.
In-Reply-To: <1426872051.1224673604360.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

    Attachment: HAMA-88_v02.patch

attach my patch.
can anyone review it?

> 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
>            Assignee: Samuel Guo
>             Fix For: 0.1.0
>
>         Attachments: HAMA-88_v01.patch, HAMA-88_v02.patch
>
>
> 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.