hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HBASE-16060) 1.x clients cannot access table state talking to 2.0 cluster
Date Tue, 05 Sep 2017 23:55:00 GMT

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

stack reassigned HBASE-16060:
-----------------------------

         Assignee: stack
    Fix Version/s:     (was: 2.0.0-alpha-3)
                   2.0.0-beta-1

Moving out of alpha3. It is off topic; i.e. is it not about API cleanup. Moved it to blocker
on beta1.

> 1.x clients cannot access table state talking to 2.0 cluster
> ------------------------------------------------------------
>
>                 Key: HBASE-16060
>                 URL: https://issues.apache.org/jira/browse/HBASE-16060
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 2.0.0-beta-1
>
>         Attachments: 0002-HBASE-16060-1.x-clients-cannot-access-table-state-ta.patch
>
>
> Since table state is migrated to meta instead of zk in 2.0, 1.x clients talking to 2.0
cluster cannot access the table state. This causes some weird behavior since from a client
perspective, {{Admin.isTableEnabled()}} and {{Admin.isTableDisabled()}} both return false.

> One option we can do is to add code in 1.x clients so that they can access the table
state in meta if needed. Otherwise, we can mirror the table state in zk (while keeping meta
as the source of truth) during 2.x lifecycle so that any 1.x client can still work correctly.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message