[
https://issues.apache.org/jira/browse/PHOENIX-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787082#comment-16787082
]
Swaroopa Kadam commented on PHOENIX-597:
----------------------------------------
[~pctony] would like me to work on this if you haven't started already?
> 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
(v7.6.3#76005)
