Actually it was relatively easy to work around PHOENIX-6377 - at least with Trino (formerly Presto) where we discovered the problem in the first place.
That said, I'll hold off Phoenix 5.x support for Trino until after Phoenix 5.1.1 as long as we can get a release out soon'ish. On Sunday, February 14, 2021, 5:04:08 AM PST, Istvan Toth <[email protected]> wrote: Thanks Viraj. Yes, if we can get HBase 2.4.1 support finished in a reasonable time, it would be nice to include it in 5.1.1. Istvan On Sun, Feb 14, 2021 at 8:37 AM Viraj Jasani <[email protected]> wrote: > Thanks Istvan, i agree to have 5.1.1 rolled out sooner due to PHOENIX-6377. > I have also merged PHOENIX-6343 to 5.1 but it’s not any blocker or strong > reason for another release as such. > > Moreover, i was thinking of supporting HBase 2.4.1 with Phoenix 5.1.1 > (PHOENIX-6359). Sounds good to you? > > > On Sat, 13 Feb 2021 at 11:41 PM, Istvan Toth <[email protected]> wrote: > > > Hi! > > > > As PHOENIX-6377 is a major problem for projects that consume the > > phoenix-client maven artifact, I think that we should release a patch > > release with the fix sooner than later. > > As soon as 4.16.0 is out, I plan to start the 5.1.1 release process from > > the 5.1 branch. > > > > Let me know your thoughts, opinion, or ideas for other fixes that should > go > > into 5.1.1. > > > > regards > > Istvan > > >
