Thanks for your information!
Then I think we can merge PR-16163 to master and release with 2.11, while
not to cherry-pick to <=2.10.
Best,
tison.
Ran Gao 于2022年6月23日周四 10:01写道：
> One problem is that the presto 334 needs jdk11+ and it didn't support
> jdk8, maybe 2.11 is a good time for Pulsar
One problem is that the presto 334 needs jdk11+ and it didn't support jdk8,
maybe 2.11 is a good time for Pulsar to upgrade the Presto to 334+ or the
latest stable version.
On 2022/06/22 18:22:09 Enrico Olivelli wrote:
> For Pulsar 2.9 and 2.10 you should use jdk11
> you can checkout the officia
For Pulsar 2.9 and 2.10 you should use jdk11
you can checkout the official docker images
for 2.11 we decided to go with jdk17
Enrico
Il giorno mer 22 giu 2022 alle ore 17:42 ZhangJian He
ha scritto:
>
> Enrico commented on 31 Mar. Now it's required jdk17 on master branch.
> `branch-2.10` is com
Enrico commented on 31 Mar. Now it's required jdk17 on master branch.
`branch-2.10` is compatible with jdk8.
Thanks
ZhangJian He
tison 于2022年6月22日周三 23:37写道：
> Hi devs.
>
> During a review of PR-16163[1] I notice a comment from @Enrico Olivelli
> on PR-14953 said:
>
> > We are currently still
Hi devs.
During a review of PR-16163[1] I notice a comment from @Enrico Olivelli
on PR-14953 said:
> We are currently still supporting jdk8 (on the server side)
However, on our README.md it recommends:
Pulsar Runtime Java Version Recommendation
pulsar master branch
Broker JavaVersion: 17
Als
