Hi Shawy and RFC-46 group, Thanks for bringing this up. Based on Alexey's latest update in another thread, the RFC-46 feature branch is going to be merged soon. It makes sense to me to let the new code fully baked in for 4 weeks and push back the code freeze date of 0.13.0 to early Jan. I'll update the 0.13.0 timeline.
Thanks, - Ethan On Wed, Nov 30, 2022 at 9:00 PM Shawy Geng <gengxiaoyu1...@gmail.com> wrote: > Hello, everyone! > > As you might be aware, community has been very busy at work on RFC-46 > aiming to bring long-awaited cutting edge level of performance to Hudi by > avoiding using Avro as an intermediate representation, instead relying on > individual engines to host data in their own formats (InternalRow for > Spark, > RowData for Flink, etc) > > We wanted to share an update in terms of where we are and what are the > next steps from here: > > - We will land phase 1 of the RFC-46 this week. > - We push the 0.13 release code-freeze by 4 weeks to make sure that RFC-46 > is fully “baked in” on master for at least 4 weeks, > allowing these changes to be picked up, worked, stretched and tested by > broader community potentially finding out any issues that we’ve not > discovered so far. > - We do code freeze for 0.13 in first week of Jan > > > Shawy Geng, on behalf of the RFC-46 group
