Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@accumulo.apache.org
Received-SPF: pass (nike.apache.org: domain of josh.elser@gmail.com designates
 209.85.214.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1399901021696-9748.post@n5.nabble.com>
References: <1399901021696-9748.post@n5.nabble.com>
Date: Mon, 12 May 2014 09:47:27 -0400
Message-ID: 
 <CAOyNEs54fqgMFLEOmsZx1oN3trh-k=ssHu7DxR4pWqCYV=Wn=Q@mail.gmail.com>
Subject: Re: Delete All Data In Table
From: Josh Elser <josh.elser@gmail.com>
To: user@accumulo.apache.org
Content-Type: multipart/alternative; boundary=089e0118254a1a32e204f93430bd

--089e0118254a1a32e204f93430bd
Content-Type: text/plain; charset=UTF-8

Not really, you enumerated the options pretty thoroughly :)

BatchDeleter is slow like you said due to pulling back all of the data to
the client and issuing deletes from there.

You could get the splits for your table (just in memory or write to disk if
they won't fit) and just re-add the splits after.

You could also try setting the DevNullIterator on the table for major
compaction and then compact it. This is just a little round about.
On May 12, 2014 9:30 AM, "BlackJack76" <justin.loy@gmail.com> wrote:

> Besides using the tableOperations to deleteRows or delete the table
> entirely,
> what is the fastest way to delete all data in a table?  I am currently
> using
> a BatchDeleter but it is extremely slow when I have a large amount of data.
> Any better options?
>
> I don't want to use the tableOperations because both the deleteRows and
> delete blow away the splits.  I would like to keep the splits in place.
>
> Appreciate your thoughts!
>
>
>
>
> --
> View this message in context:
> http://apache-accumulo.1065345.n5.nabble.com/Delete-All-Data-In-Table-tp9748.html
> Sent from the Users mailing list archive at Nabble.com.
>

--089e0118254a1a32e204f93430bd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Not really, you enumerated the options pretty thoroughly :)<=
/p>
<p dir=3D"ltr">BatchDeleter is slow like you said due to pulling back all o=
f the data to the client and issuing deletes from there. </p>
<p dir=3D"ltr">You could get the splits for your table (just in memory or w=
rite to disk if they won&#39;t fit) and just re-add the splits after. </p>
<p dir=3D"ltr">You could also try setting the DevNullIterator on the table =
for major compaction and then compact it. This is just a little round about=
. </p>
<div class=3D"gmail_quote">On May 12, 2014 9:30 AM, &quot;BlackJack76&quot;=
 &lt;<a href=3D"mailto:justin.loy@gmail.com">justin.loy@gmail.com</a>&gt; w=
rote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Besides using the tableOperations to deleteRows or delete the table entirel=
y,<br>
what is the fastest way to delete all data in a table? =C2=A0I am currently=
 using<br>
a BatchDeleter but it is extremely slow when I have a large amount of data.=
<br>
Any better options?<br>
<br>
I don&#39;t want to use the tableOperations because both the deleteRows and=
<br>
delete blow away the splits. =C2=A0I would like to keep the splits in place=
.<br>
<br>
Appreciate your thoughts!<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-accumulo.1065345.n5.=
nabble.com/Delete-All-Data-In-Table-tp9748.html" target=3D"_blank">http://a=
pache-accumulo.1065345.n5.nabble.com/Delete-All-Data-In-Table-tp9748.html</=
a><br>

Sent from the Users mailing list archive at Nabble.com.<br>
</blockquote></div>

--089e0118254a1a32e204f93430bd--