I prefer we still support JDK8 for 3.0.0, and then add JDK17 support and
drop JDK8 for 4.0.0.
We could do this in the second half of this year after we cut branch-3.
Stack 于2021年5月28日周五 上午8:38写道：
> On Thu, May 27, 2021 at 7:34 AM Wellington Chevreuil <
> wellington.chevre...@gmail.com> wrote:
>
On Thu, May 27, 2021 at 7:34 AM Wellington Chevreuil <
wellington.chevre...@gmail.com> wrote:
> ... I guess this was
> not expected, and our official goal is to still support jdk8 for the
> upcoming 3.0 release?
>
I'd suggest dropping jdk8 support in hbase3.
S
Thanks Andrew!
On Thu, 27 May 2021, 17:25 Andrew Purtell, wrote:
> There is a JIRA for using the new —release build flag available in JDK 9+
> to safely build binaries meant to run on JDK8. See
> https://issues.apache.org/jira/browse/HBASE-25465
>
> This issue with the ByteBuffer signature chang
There is a JIRA for using the new —release build flag available in JDK 9+ to
safely build binaries meant to run on JDK8. See
https://issues.apache.org/jira/browse/HBASE-25465
This issue with the ByteBuffer signature change and linkage problems is exactly
what motivated me to look into it.
> O
I had faced below errors when trying to run current master branch version
on jdk8 (build was also on jdk8):
2021-05-26T23:02:20,202 TRACE [RS-EventLoopGroup-1-1]
ipc.NettyRpcServer: Connection /192.168.56.105:44592; caught
unexpected downstream exception.
> java.lang.NoSuchMethodError: java.nio.By
