Yes the IT failure is relevant, and Lokesh has confirmed issue with MapReduce jobs referring to closed connection hence yes this would be binding of -1 from my side as well.
The changes are reverted from all applicable branches. We can resume with next RC once Tanuj is back. On Tue, Nov 22, 2022 at 8:30 AM Geoffrey Jacoby <gjac...@apache.org> wrote: > Viraj, is that a binding vote of -1? > > I haven't had a chance to test the RC yet, but if the IT test was failing > in 5.1 similarly to how it was failing in master due to PHOENIX-6776, I > concur. > > -1 (binding) for me. > > On Tue, Nov 22, 2022 at 3:21 AM Viraj Jasani <vjas...@apache.org> wrote: > > > Since PHOENIX-6776 is reverted, we will need new RC for 5.1.3. > > > > > > On Sun, Nov 13, 2022 at 12:51 PM Tanuj Khurana <tkhur...@apache.org> > > wrote: > > > > > Please vote on this Apache phoenix release candidate, phoenix-5.1.3RC0 > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > [ ] +1 Release this package as Apache phoenix 5.1.3 > > > [ ] -1 Do not release this package because ... > > > > > > The tag to be voted on is 5.1.3RC0: > > > > > > https://github.com/apache/phoenix/tree/5.1.3RC0 > > > > > > The release files, including signatures, digests, as well as CHANGES.md > > > and RELEASENOTES.md included in this RC can be found at: > > > > > > https://dist.apache.org/repos/dist/dev/phoenix/5.1.3RC0/ > > > > > > Maven artifacts are available in a staging repository at: > > > > > > https://repository.apache.org/content/repositories// > > > > > > Artifacts were signed with the 0x47BBA537 key which can be found in: > > > > > > https://dist.apache.org/repos/dist/release/phoenix/KEYS > > > > > > To learn more about Apache phoenix, please see > > > > > > https://phoenix.apache.org/ > > > > > > Thanks, > > > Tanuj Khurana > > > > > >
