We can include the block token work that is in the process of being merged.
That work considerably impacts performance, and delaying it to 1.5.0 will
lead to a negative experience with a secure Ozone cluster for
folks adopting Ozone in 1.4.0
Regards,
Ritesh
On Wed, Jun 7, 2023 at 9:49 AM Ethan Ros
+1 for a 1.4.0 release. We had hoped for a 1.3.1 release but it looks like
that never gained the momentum it needed. It would be good to hear from
devs working on larger features whether or not they would like to target
this release. Things like snapshots, cert rotation, hsync, recon
improvements e
Shoot your shot!
-- Forwarded message -
From: Duo Zhang
Date: Mon, Jun 5, 2023 at 7:37 PM
Subject: Fwd: Call for Presentations, Community Over Code Asia 2023
To: HBase Dev List , hbase-user ,
user-zh
FYI. The CFP deadline has been extended to 6.18, please submit your
representa
Dear Ozone Devs,
It's been almost 5 month since the last major 1.3.0 release in Dec 2022.
In the past 5 month, there have been a lot of issues fixed and improvements
made, together with new features, like httpFs, scm decommission, Recon new
functions, snapshot, EC balancer support, the the coming
I see. Thanks @Wei-Chiu Chuang for the confirmation.
On Wed, 31 May 2023 at 05:08, Wei-Chiu Chuang wrote:
> I had the same question too. If I look at the HDFS implementation as the
> reference, HDFS setTimes() touches only the directory/file specified. It
> doesn't do anything else. Therefore i
