[DISCUSS] Delay code freeze date for next release until Jan 19th (Sunday)

2020-01-15 Thread leesf
Dear Community, As discussed in the weekly sync meeting, we marked that there are 5 blockers[1] that should be resolved before cutting next release, and kindly welcome to review these PRs[2]. Regrading Jan 15th is a bit tight to get them all on land. I propose to delay the code freeze date until

contributor permission

2020-01-15 Thread wangkuan
Hi, I want to contribute to Apache Hudi. Would you please give me the contributor permission? My JIRA ID is wangkuan9527.

Re: [DISCUSS] Delay code freeze date for next release until Jan 19th (Sunday)

2020-01-15 Thread Vinoth Chandar
+1 from me. I feel sunday is good in general, because the weekend gives enough time for taking care of last minute things On Wed, Jan 15, 2020 at 2:11 AM leesf wrote: > Dear Community, > > As discussed in the weekly sync meeting, we marked that there are 5 > blockers[1] that should be resolved

Re: [DISCUSS] Delay code freeze date for next release until Jan 19th (Sunday)

2020-01-15 Thread Balaji Varadarajan
+1 Sunday should give breathing space to fix the blockers. Balaji.V On Wednesday, January 15, 2020, 06:50:28 AM PST, Vinoth Chandar wrote: +1 from me. I feel sunday is good in general, because the weekend gives enough time for taking care of last minute things On Wed, Jan 15, 2020 at

Re: contributor permission

2020-01-15 Thread Vinoth Chandar
Done! Welcome aboard! On Wed, Jan 15, 2020 at 1:21 AM wangkuan <346795...@qq.com> wrote: > Hi, > > I want to contribute to Apache Hudi. Would you please give me the > contributor permission? My JIRA ID is wangkuan9527.

Re: [DISCUSS] Delay code freeze date for next release until Jan 19th (Sunday)

2020-01-15 Thread nishith agarwal
+1, sunday sounds good. -Nishith On Wed, Jan 15, 2020 at 9:08 AM Balaji Varadarajan wrote: > +1 Sunday should give breathing space to fix the blockers. > Balaji.V > On Wednesday, January 15, 2020, 06:50:28 AM PST, Vinoth Chandar < > vin...@apache.org> wrote: > > +1 from me. I feel sunday

Re: [DISCUSS] Rename the name of hudi-hadoop-mr module

2020-01-15 Thread leesf
Thanks vino for bringing up the discussion. +1 to rename the module name as the name is not very suitable, and hudi-query-common/hudi-query-bundle sounds resonable. Best, Leesf vino yang 于2020年1月16日周四 下午1:56写道: > Hi guys, > > I want to start a proposal about refactoring the naming of the >

Re: Dec 17, 2019 Meeting notes

2020-01-15 Thread leesf
Hi, Sorry for late repsponse. Since hangouts is blocked in china, to encorage more people in china to participate, we could use skype( https://web.skype.com/ ) for weekly sync meeting and may give it a try. Besides I would like to count the number of people in China who want to participate in

Re: [DISCUSS] Delay code freeze date for next release until Jan 19th (Sunday)

2020-01-15 Thread Y Ethan Guo
+1, this allows more time to land critical PRs. On Wed, Jan 15, 2020 at 10:54 PM leesf wrote: > > I assume you meant UTC-8  > Sure :) >

Re: [DISCUSS] Delay code freeze date for next release until Jan 19th (Sunday)

2020-01-15 Thread leesf
> I assume you meant UTC-8  Sure :)

[DISCUSS] Rename the name of hudi-hadoop-mr module

2020-01-15 Thread vino yang
Hi guys, I want to start a proposal about refactoring the naming of the "hudi-hadoop-mr" module. IMHO, this module name is not user-friendly. It may make users confused. Because it looks like that it's about integrating with MapReduce( although I know it referenced parquet-mr[1] project). Based

Re: [DISCUSS] Delay code freeze date for next release until Jan 19th (Sunday)

2020-01-15 Thread Shiyan Xu
+1 I assume you meant UTC-8  On Wed, 15 Jan 2020, 11:26 nishith agarwal, wrote: > +1, sunday sounds good. > > -Nishith > > On Wed, Jan 15, 2020 at 9:08 AM Balaji Varadarajan > wrote: > > > +1 Sunday should give breathing space to fix the blockers. > > Balaji.V > > On Wednesday, January