Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of varun@pinterest.com designates
 209.85.219.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKxWWm23tEuwquOkXT4u31shNW9AeatZvUOBU-hrhqRfNb6wXg@mail.gmail.com>
References: 
 <CAKxWWm23tEuwquOkXT4u31shNW9AeatZvUOBU-hrhqRfNb6wXg@mail.gmail.com>
Date: Sun, 30 Jun 2013 12:35:57 -0700
Message-ID: 
 <CAKxWWm1_Spy6kk7z-3rePDV0_kjGMq=7pNvc+i7-2kaVirq4TQ@mail.gmail.com>
Subject: Re: Issues with delete markers
From: Varun Sharma <varun@pinterest.com>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>, user@hbase.apache.org
Content-Type: multipart/alternative; boundary=089e0160c35a9a0a7e04e064387d

--089e0160c35a9a0a7e04e064387d
Content-Type: text/plain; charset=ISO-8859-1

I tried this a little bit and it seems that filters are not called on
delete markers. For raw scans returning delete markers, does it make sense
to do that ?

Varun


On Sun, Jun 30, 2013 at 12:03 PM, Varun Sharma <varun@pinterest.com> wrote:

> Hi,
>
> We are having an issue with the way HBase does handling of deletes. We are
> looking to retrieve 300 columns in a row but the row has tens of thousands
> of delete markers in it before we span the 300 columns something like this
>
>
> row  DeleteCol1 Col1  DeleteCol2 Col2 ................... DeleteCol3 Col3
>
> And so on. Therefore, the issue here, being that to retrieve these 300
> columns, we need to go through tens of thousands of deletes - sometimes we
> get a spurt of these queries and that DDoSes a region server. We are okay
> with saying, only return first 300 columns and stop once you encounter, say
> 5K column delete markers or something.
>
> I wonder if such a construct is provided by HBase or do we need to build
> something on top of the RAW scan and handle the delete masking there.
>
> Thanks
> Varun
>
>
>

--089e0160c35a9a0a7e04e064387d--