Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 12 Jun 2011 11:14:51 +0000 (UTC)
From: "kristam subba swathi (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <2048572170.734.1307877291650.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-6) Opening then closing a scanner delays
 the effects of a delete
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048294#comment-13048294 ] 

kristam subba swathi commented on HBASE-6:
------------------------------------------

if we delete the column using admin.deletecolumn API,we need not use this table.delete(delete) again...but if we delete the column using delete.deletecolumn API ,then we should use table.delete(delete)(here table is a htable object)

> Opening then closing a scanner delays the effects of a delete
> -------------------------------------------------------------
>
>                 Key: HBASE-6
>                 URL: https://issues.apache.org/jira/browse/HBASE-6
>             Project: HBase
>          Issue Type: Bug
>          Components: client
>            Reporter: Clint Morgan
>         Attachments: HADOOP-2542.patch
>
>
> I stumbled across the following odd behavior: When I open, then close a scanner on
> a table, then delete a row in the table, the delete does not work
> (i.e., I can still get the row).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira