Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of patrick.schless@gmail.com
 designates 209.85.223.169 as permitted sender)
MIME-Version: 1.0
From: Patrick Schless <patrick.schless@gmail.com>
Date: Mon, 17 Jun 2013 14:20:31 -0500
Message-ID: 
 <CAJOxyf1zJBz5sZWMjqMUskerJDt5W=Ce3NCOZTHWpH7V4M13-Q@mail.gmail.com>
Subject: CopyTable
To: user <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=089e0112cedcadb10804df5e7e92

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

Context:
I'm working on getting replication set up, and a prerequisite for me is to
rename the table (since you have to replicate to the same name as the
source). For this, I'm testing a CopyTable strategy, since there doesn't
seem to be a good way to rename a table (please correct me if I'm wrong).

My question:
According to [1], the CopyTable job takes an argument "all.cells" which "Also
copy delete markers and uncollected deleted cells (advanced option)."

I'm confused by the "advanced option" bit. When would you not want to copy
deletes over to a new table? Without that, it seems like you could end up
with more data than you were expecting in the target table.

Any info would be helpful.

Thanks,
Patrick


[1] http://hbase.apache.org/book/ops_mgt.html#copytable

--089e0112cedcadb10804df5e7e92--