[
https://issues.apache.org/jira/browse/HBASE-24353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107408#comment-17107408
]
Michael Stack edited comment on HBASE-24353 at 5/14/20, 3:34 PM:
-----------------------------------------------------------------
Thank you [~DeanZ] for the info.
In my case, the compare of table schemas was failing because I could not make
them the same even after altering the table schema; hbase1 did not have the
NEW_VERSION_BEHAVIOR define: see PR in the sub-issue:
https://patch-diff.githubusercontent.com/raw/apache/hbase/pull/1696.patch
Your info makes me think this might be only change needed to make an hbase1
replicate into an hbase2. Thanks again for the info.
was (Author: stack):
Thank you [~DeanZ] for the info.
In my case, the compare of table schemas was failing because I could not make
them the same even after altering the table schema; hbase1 did not have the
NEW_VERSION_BEHAVIOR define:
https://patch-diff.githubusercontent.com/raw/apache/hbase/pull/1696.patch
Your info makes me think this might be only change needed to make an hbase1
replicate into an hbase2. Thanks again for the info.
> Allow hbase1 cluster to replicate to an hbase2 cluster
> ------------------------------------------------------
>
> Key: HBASE-24353
> URL: https://issues.apache.org/jira/browse/HBASE-24353
> Project: HBase
> Issue Type: Umbrella
> Components: Replication
> Reporter: Michael Stack
> Priority: Major
>
> Umbrella issue to make it so an hbase1 cluster can replicate to an hbase2
> cluster. I thought this worked but just tried it and it doesn't seem like it
> can. Replication compares table schemas before it starts. The hbase2 has a
> default that is not defined in hbase1 so we are unable to make the schemas
> equivalent. There are probably other issues in here too. Let me make an
> umbrella.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
