+1. Since ETag feature already landed on ozone-1.4 branch. I also propose to
include ETag related fixes / improvements in version 1.4.1.
HDDS-9680. Use md5 hash of multipart object part's content as ETag
(#5668)HDDS-10395. Fix eTag compatibility issues during MPU (#6235)HDDS-10403.
CopyObject should set ETag based on the key content (#6251)HDDS-10521. ETag
field should not be returned during GetObject if the key does not contain ETag
field (#6377)HDDS-10587. Reset the thread-local MessageDigest instance during
exception (#6435)
All these fixes have been backported to our internal cluster and currently they
are working well.
On Monday, April 8, 2024 at 06:52:43 AM GMT+8, Tsz Wo Sze
<szets...@gmail.com> wrote:
+1 It is good to release Ozone 1.4.1. Let's also update the Ratis version.
Tsz-Wo
On Sun, Apr 7, 2024 at 4:28 AM wanghongbing <whbing.w...@foxmail.com> wrote:
> +1, Releasing 1.4.1 is meaningful.
>
>
> > On Apr 3, 2024, at 13:15, Sammi Chen <sammic...@apache.org> wrote:
> >
> > Dear Ozone Devs,
> >
> > We have released 1.4.0 on Jan 19th.
> > Now there are 51 new commits already landed on 1.4.0 branch
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HDDS%20AND%20fixVersion%20%3D%201.4.1
> >
> > and 21 targeting 1.4.1, but not landed on the branch yet,
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HDDS%20AND%20%22Target%20Version%2Fs%22%20%3D%201.4.1%20AND%20fixVersion%20!%3D%201.4.1%20ORDER%20BY%20resolved%20ASC
> >
> > I would like to propose starting the 1.4.1 release now. What do you
> think?
> >
> > And Xi Chen has volunteered to be the RM of 1.4.1.
> >
> > Regards,
> > Sammi
>
>
