Having a formal policy on maintaining HBase support would provide a peace
of mind to users.

* When do we drop support for minor HBase releases ?
  * As soon as they are EOL ?
  * Do we want to declare a grace period ?
* What happens if a new HBase patch release is incompatible ?
  * We may want to keep the old compatibility module in the code if we have
already released a version where it is supported
* Do we drop support for HBase releases in Phoenix patch versions ?
(provided we plan to release them in the future)
   * So far we didn't make an issue of dropping support for older HBase
patch releases in master, as we didn't have a release that supports
them anyway.

Dropping Hbase 1.3 support would allow for a major simplification in the
compat code.
Dropping the rest of the versions wouldn't buy us much (apart from CI
resource usage)

Istvan

On Fri, Jan 29, 2021 at 5:57 AM Viraj Jasani <vjas...@apache.org> wrote:

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


-- 
*István Tóth* | Staff Software Engineer
st...@cloudera.com <https://www.cloudera.com>
[image: Cloudera] <https://www.cloudera.com/>
[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
<https://www.cloudera.com/>
------------------------------

Reply via email to