You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/01/24 05:13:39 UTC
[jira] [Updated] (PHOENIX-597) Detect if HBase table exists and is
not split as expected when DDL run
[ https://issues.apache.org/jira/browse/PHOENIX-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-597:
---------------------------------
Assignee: (was: Aakash Pradeep)
> Detect if HBase table exists and is not split as expected when DDL run
> ----------------------------------------------------------------------
>
> Key: PHOENIX-597
> URL: https://issues.apache.org/jira/browse/PHOENIX-597
> Project: Phoenix
> Issue Type: Task
> Reporter: James Taylor
>
> Currently, if you create an unsplit or unsalted table like this:
> CREATE TABLE t (k VARCHAR PRIMARY KEY);
> and then drop it:
> DROP TABLE k;
> and the create it again, either salted or split:
> CREATE TABLE t (k VARCHAR PRIMARY KEY) SALT_BUCKETS=10;
> Then it's not going to work properly, since the second CREATE will not pre-split the table since the HBase table already exists (as we currently never drop HBase metadata).
> We should either drop the HBase metadata on DROP TABLE, or we should at a minimum detect this case and throw.
> As a workaround, when creating a salted or split table, make sure to disable and drop it from the HBase shell if it already exists.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)