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 2020/08/04 05:20:00 UTC

[jira] [Commented] (TEPHRA-309) Add HBase 1.5 and 1.6 compatibility

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

Istvan Toth commented on TEPHRA-309:
------------------------------------

I have noticed that HBase 1.5 support is added in TEPHRA-301, but there were some problems with adding it the usual way (new module subproject, examples)

As part of the 1.6 work, it may be useful to try add the submodules for it again, to gain test coverage.

> Add HBase 1.5 and 1.6 compatibility
> -----------------------------------
>
>                 Key: TEPHRA-309
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-309
>             Project: Phoenix Tephra
>          Issue Type: Task
>    Affects Versions: 0.15.0-incubating
>            Reporter: Istvan Toth
>            Assignee: Poorna Chandra
>            Priority: Critical
>
> We have added support for HBase 1.5 and 1.6 in Phoenix, but not in Tephra.
> While this is not detected by the Phoenix test suite due to the simplified Tephra implementation it uses with minicluster, this means that Phoenix 4.x on HBase 1.5 and 1.6 cannot use Tephra on a real cluster.
> The 1.5 and 1.6 compat modules can probably share code (like 2.0 2.1 and 2.2 does), and may possibly even re-use the 1.4 compat code.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)