+1(non-binding) to EOLing the support for HBase 1.3 and 2.1 at least since both were EOLed last year (1.4 and 2.2 can also be dropped).
Moreover, b/ 2.4.0 and 2.4.1 we have some compat issue in IA.Private class (we need some utility from HStore which is refactored in 2.4.1), hence we will need new compat module to support 2.4.1+ releases in Phoenix 5.2.0+ releases mostly. On Fri, 29 Jan 2021 at 6:54 AM, Geoffrey Jacoby <gjac...@apache.org> wrote: > +1. Following 4.16 and 5.1's releases I'd suggest EOLing support for HBase > 1.3, 1.4, 2.1 and 2.2, I believe all of which have been EOLed by the HBase > community. All of those versions also require special compatibility lib > support currently. > > Geoffrey > > On Thu, Jan 28, 2021 at 6:35 PM Xinyi Yan <yanxi...@apache.org> wrote: > > > Hi, > > > > I'm thinking to drop the number of supported HBase versions for future > > releases. For example, the HBase 1.3 was EOM'd in August 2020, do we > still > > consider support it for 4.17.0? Similarly, our current master branch also > > supports EOM'd HBase version. If phoenix users already upgraded their > > HBase, we should not spend time supporting these old versions IMO. > > > > I think we should do it after 4.16.0 and 5.1.0, thoughts? > > > > > > Thanks, > > Xinyi > > >
