Hi Shilun,
Thanks for your great work!
Compare branch-3.4 and branch-3.4.0, I found that commit [1]
is only checked in branch-3.4.0 but not branch-3.4. Please double
check if we need to backport branch-3.4.
Moreover, before 3.4.0 release we should cherry-pick from trunk
to branch-3.4 first if
Thank you for reporting this issue and I will follow up on HDFS-17129.
I acknowledge that I haven't checked for those marked as critical/blocker
in RC0. I intend to complete this check before the release of RC1.
Thank you again for your valuable suggestions!
Best Regards
Shilun Fan.
Ayush
We should consider including
https://issues.apache.org/jira/browse/HDFS-17129
Which looks like inducing some misorder between IBR & FBR which can
potentially lead to strange issues, if that can’t be merged, should revert
the one which causes that.
I think we should check for any ticket which has
Thank you very much for your help in verifying this version! We will use
version 3.5.0 for fix jira in the future.
Best Regards,
Shilun Fan.
> wonderful! I'll be testing over the weekend
> Meanwhile, new changes I'm putting in to trunk are tagged as fixed in
3.5.0
> -correct?
> steve
>
wonderful! I'll be testing over the weekend
Meanwhile, new changes I'm putting in to trunk are tagged as fixed in 3.5.0
-correct?
steve
On Thu, 11 Jan 2024 at 05:15, slfan1989 wrote:
> Hello all,
>
> We plan to release hadoop 3.4.0 based on hadoop trunk, which is the first
> hadoop 3.4.0-RC
Thanks for driving this release, Shilun Fan.
The top page of site documentation (in hadoop-3.4.0-RC0-site.tar.gz)
looks the same as 3.3.5.
While the index.md.vm is updated in branch-3.4.0[1], it seems not to be
reflected.
release-3.4.0-RC0 tag should be pushed to make checking easier.
In
