phoenix-issues mailing list archives

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

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

Josh Elser commented on PHOENIX-5268:
-------------------------------------

{quote} I think we should implement ExtendedCell for the server side Cell, but ExtendedCell
also is a Private class
{quote}
We'll have to do an unsafe cast for this, I think. I see in the LocalIndexing code, we have
at least one place we call {{setSequenceId(long)}}. I've not yet gotten to the global indexing
code yet, but assuem that we'll have something there.

There's been a lot I've been able to unwind purely from assumptions Phoenix makes about how
a KeyValue gets serialized (which is our biggest problem).

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