[
https://issues.apache.org/jira/browse/PHOENIX-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445625#comment-17445625
]
ASF GitHub Bot commented on PHOENIX-6587:
-----------------------------------------
stoty commented on pull request #1353:
URL: https://github.com/apache/phoenix/pull/1353#issuecomment-972530518
> Do we already prevent create table on preexisting table with salt set?
I wouldn't want to prevent that.
Copying/Loading a Phoenix data table with HBase tools into a cluster, and
then running _create table_ to re-create the Phoenix metadata is a supported
and standard procedure, (even if I have seen people messing that up.)
I haven't tested it, but as we're not creating a new HBase table, we
probably either error out, or just ignore the pre-split points in this case.
I'm going to try out what happens in this case.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@phoenix.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Disallow specifying explicit pre-split on salted tables
> -------------------------------------------------------
>
> Key: PHOENIX-6587
> URL: https://issues.apache.org/jira/browse/PHOENIX-6587
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Minor
>
> Specifying the split points manually on salted tables can break them.
> The easiest thing to do is to disallow it, which ensures that the table is
> created with the default per bucket presplit.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
