You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2022/08/23 15:47:00 UTC

[jira] [Resolved] (OMID-223) Refactor Omid to use HBase 2 APIs internally

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

Istvan Toth resolved OMID-223.
------------------------------
    Fix Version/s: 1.0.3
       Resolution: Fixed

Committed to master.


I have also added myself as a co-athor, as this is based on my WIP patch.

Thanks a lot for hashing this out [~ameszaros] , and for the reviews [~gjacoby] .

> Refactor Omid to use HBase 2 APIs internally
> --------------------------------------------
>
>                 Key: OMID-223
>                 URL: https://issues.apache.org/jira/browse/OMID-223
>             Project: Phoenix Omid
>          Issue Type: Improvement
>            Reporter: Istvan Toth
>            Assignee: Aron Attila Meszaros
>            Priority: Major
>             Fix For: 1.0.3
>
>         Attachments: OMID-223-wip.patch
>
>
> Omid currently uses HBase 1 APIs everywhere. 
> This made sense when HBase 1 and 2 had to be supported from the same codebase.
> However, as we're dropping HBase 1 support, this is a liability now.
> Doing this is also going to eventually make supporting HBase 3 much easier.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)