You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2020/05/12 19:37:00 UTC

[jira] [Resolved] (HBASE-24354) Make it so can make an hbase1 schema and hbase2 schema equate

     [ https://issues.apache.org/jira/browse/HBASE-24354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Stack resolved HBASE-24354.
-----------------------------------
    Fix Version/s: 2.3.0
                   3.0.0-alpha-1
         Assignee: Michael Stack
       Resolution: Fixed

Pushed after testing an hbase1 replicating to an hbase2.

> 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)