phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5268) HBase 2.0.5 compatibility
Date Wed, 22 May 2019 21:53:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846246#comment-16846246
] 

Lars Hofhansl commented on PHOENIX-5268:
----------------------------------------

I think the eventual plan is to get rid of IndexedKeyValue. With the coming implementation
of global secondary indexes (PHOENIX-5211, PHOENIX-5156) in theory there's no need to persist
the index changes into the WAL of the main table, and we could remove IndexedKeyValue completely.
[~kozdemir].

> HBase 2.0.5 compatibility
> -------------------------
>
>                 Key: PHOENIX-5268
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5268
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 5.1.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> HBASE-21754 introduces a new abstract method to RpcScheduler: {{getMetaPriorityQueueLength()}}
> This means that Phoenix does not build against HBase 2.0.5.
> FYI [~twdsilva@gmail.com], [~Jaanai].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message