[
https://issues.apache.org/jira/browse/HBASE-24354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159996#comment-17159996
]
Michael Stack commented on HBASE-24354:
---------------------------------------
I did not include the exception seen when we had this issue which was a mistake
if only because it made it harder to turn up this Jira in search.
It this one in HBaseAdmin:
{color:#000080}throw new {color}IllegalArgumentException({color:#008000}"Table
" {color}+ tableName.getNameAsString()
+ {color:#008000}" exists in peer cluster " {color}+ peerDesc.getPeerId()
+ {color:#008000}", but the table descriptors are not same when compared with
source cluster."
{color} + {color:#008000}" Thus can not enable the table's replication
switch."{color});
> Make it so can make an hbase1 schema and hbase2 schema equate
> -------------------------------------------------------------
>
> Key: HBASE-24354
> URL: https://issues.apache.org/jira/browse/HBASE-24354
> Project: HBase
> Issue Type: Sub-task
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
>
> Currently, NEW_VERSION_BEHAVIOR displays in hbase2 schemas with default value
> of 'false'. This default is added whenever we create a new column descriptor.
> Its not needed. We'll return default if empty or undefined. Meantime, since
> this is not defined in hbase1, it makes it so we can't make equivalent
> schemas so not possible to replicate from hbase1 to hbase2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
