[
https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056217#comment-17056217
]
Istvan Toth commented on PHOENIX-5607:
--------------------------------------
[~ckulkarni] No problem, this is very new.
Yes, the idea is that the 4.x-HBase-1.* branches are obsoleted by this.
With the unified 4.x, the supported HBase version is determined by which compat
module you put on the classpath, and there is no easy way to tell which one is
loaded from the code. It would be easy to add a version class to the compat
module for that, though.
(The profile really just selects which compat module is shaded into the
uberJars)
If you need it, I'd read the HBase client version directly from HBase, that's
the easiest and most accurate way to find it out.
> Client-server backward compatibility tests
> -------------------------------------------
>
> Key: PHOENIX-5607
> URL: https://issues.apache.org/jira/browse/PHOENIX-5607
> Project: Phoenix
> Issue Type: Test
> Affects Versions: 4.15.0
> Reporter: Lars Hofhansl
> Assignee: Sandeep Guggilam
> Priority: Blocker
> Labels: phoenix-hardening
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch,
> PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch,
> PHOENIX-5607.4.x-HBase-1.3.v4.patch, PHOENIX-5607.4.x-HBase-1.3.v5.patch,
> PHOENIX-5607.master.v1.patch
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Filing this as a blocker for 4.16.0.
> As we've seen with the various failed attempts to release 4.15.0 Phoenix'
> backwards compatibility story is weak, and lacks tests - in fact there're no
> tests.
> We should not allow to ship 4.16.0 without improving that and without tests.
> [~ckulkarni], [~gjacoby] , FYI, what we discussed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
