Thanks Istvan.  This is useful for now.

I will (try and) build from the trunk and use it against HBase2.1 for
development & migration purpose.

One we are ready, we hope there would be a certified release (5.1) too.

~JAK

On Wed, Apr 22, 2020 at 10:27 AM Istvan Toth <st...@apache.org> wrote:

> The Apache Phoenix master branch works with all supported (i.e. not EOL)
> HBase 2.x branches ( 2.1 and 2.2, and for now even 2.0, though it's EOL),
> and we aim to keep it that way.
>
> The plan is to support all active HBase 2.x branches at the time of
> release of Phoenix 5.1.
>
> No comment on dates.
>
> Istvan
>
> On Tue, Apr 21, 2020 at 6:57 PM Arun J <mail....@gmail.com> wrote:
>
>> Thanks Josh.
>>
>> That means the last supported HBase version is 2.0 (phoenix5.0). CDH
>> claims support for Hbase2.1.x as part of its 6.2 parcels hence I was
>> confused.
>>
>> Any info on what would be the next supported HBase version and when?
>>
>> JAK
>>
>>
>> On Tue, Apr 21, 2020, 10:09 PM Josh Elser <els...@apache.org> wrote:
>>
>>> Please read the website for information on Apache Phoenix releases.
>>>
>>> http://phoenix.apache.org/download.html
>>>
>>> On 4/20/20 3:35 PM, Arun J wrote:
>>> > What is the latest HBase version that Apache Phoenix 5.x support?
>>> >
>>> > We are forced to explore at both CDH and non-CDH options.
>>> >
>>> > CDH claims Phoenix 5.0 parcel for CDH 6.2+ but not sure of HBase
>>> version
>>> > while CDH6.2.3 packages HBase2.1.0.  Since CDH is discontinuing the
>>> > community version - we are exploring options outside of it hence
>>> > checking what the latest HBase version Phoenix support.
>>> >
>>> >  >> Cloudera has released a Phoenix 4.14.1 parcel
>>> > <
>>> https://www.cloudera.com/documentation/enterprise/5/latest/topics/phoenix_installation.html>available
>>>
>>> > to CDH 5.16.2 customers and Phoenix 5.0 parcel available to CDH 6.2+
>>> > customers.
>>> >
>>> >
>>> > On Mon, Apr 20, 2020 at 8:49 PM Josh Elser <els...@apache.org
>>> > <mailto:els...@apache.org>> wrote:
>>> >
>>> >     You should contact Cloudera for information on how to use Phoenix
>>> on
>>> >     CDH.
>>> >
>>> >     There is no upstream build of Apache Phoenix 5.x which was built
>>> and
>>> >     tested against any release of CDH. There is only the downstream
>>> work
>>> >     which Cloudera packages and provides themselves.
>>> >
>>> >     On 4/20/20 11:09 AM, Arun J wrote:
>>> >      >
>>> >      > All,
>>> >      >
>>> >      > I see that the latest support HBase version is 2.0 from the
>>> below
>>> >      > listing here <http://phoenix.apache.org/download.html>
>>> >      >
>>> >      > We use CDH6.3.2 which is documented to be HBase 2.14 however it
>>> uses
>>> >      > HBase 2.1.0.  Looking to use Phoenix on this CDH ecosystem but
>>> >     not sure
>>> >      > whether there is a supported version against this HBase (2.1).
>>> >       This
>>> >      > CDH version is the last community version and I am thinking many
>>> >     would
>>> >      > be on this HBase (2.1) version.
>>> >      >
>>> >      > There are some aggregated functions that is supported in HBase
>>> 2x
>>> >     and I
>>> >      > am curious to see whether Phoenix supports and leverages those
>>> >     and if
>>> >      > there is a supported version on 2.1.  I saw this thread but I
>>> >     couldn't
>>> >      > get anything concrete finalized.
>>> >      >
>>> >      >
>>> >
>>> https://lists.apache.org/thread.html/210c38fad6b42251bfac67d778577e356944dea7f9baa20526d64c76%40%3Cdev.phoenix.apache.org%3E
>>> >      >
>>> >      > I also found the release date is July 2018 for HBase 2.0 whereas
>>> >      > HBase1.5 is Dec 2019.  Is this release date accurate.  I am
>>> little
>>> >      > confused with the  chronology of dates below.  Any release
>>> >     further to
>>> >      > this on HBase 2.x?
>>> >      >
>>> >      > TIA,
>>> >      > JAK
>>> >      >
>>> >      > Version       Release Date
>>> >      > 5.0.0-HBase-2.0       04/jul/2018
>>> >      >
>>> >      > 4.15.0-HBase-1.5      20/dec/2019
>>> >      >
>>> >      > 4.15.0-HBase-1.4      20/dec/2019
>>> >      >
>>> >
>>>
>>

Reply via email to