Re: [Discuss] Apache Kylin Component Owner Plan

+1 Best Regards! - Luke Han On Fri, Feb 9, 2018 at 1:51 PM, Dayue Gao wrote: > +1 > I would like to be a backup owner for the "Storage-HBase" component. > Thanks. > > > Regards, > Dayue Gao > > At 2018-02-09 12:41:16, "Yerui Sun"

Re: [Discuss] Apache Kylin Component Owner Plan

+1 I would like to be a backup owner for the "Storage-HBase" component. Thanks. Regards, Dayue Gao At 2018-02-09 12:41:16, "Yerui Sun" wrote: >I’d like to take storage-hbase component, thanks. > >> 在 2018年2月5日，09:56，yu feng 写道： >> >> may I take JDBC

Re: [Discuss] Apache Kylin Component Owner Plan

I’d like to take storage-hbase component, thanks. > 在 2018年2月5日，09:56，yu feng 写道： > > may I take JDBC components, and backup with @Dong Li , Thanks. > > 2018-02-05 9:11 GMT+08:00 Jianhua Peng >: > >> +1. >> >> I

Re: [Discuss] Apache Kylin Component Owner Plan

Thanks everyone; Now most components have owners; The following components have not yet, still open for volunteers: Client - CLI Environment Storage - HBase Tools, Build and Test Others 2018-02-05 9:56 GMT+08:00 yu feng : > may I take JDBC components, and backup with

Re: [Discuss] Apache Kylin Component Owner Plan

may I take JDBC components, and backup with @Dong Li , Thanks. 2018-02-05 9:11 GMT+08:00 Jianhua Peng : > +1. > > I would like to take the ownership of "Security" components. > I also could be a backup owner for "Job Engine" components. > > Best regards, > Jianhua Peng >

Re: [Discuss] Apache Kylin Component Owner Plan

+1. I would like to take the ownership of "Security" components. I also could be a backup owner for "Job Engine" components. Best regards, Jianhua Peng On 2018/02/02 02:39:38, ShaoFeng Shi wrote: > Hello, Kylin community, > > In the past, we don't have a clear rule

Re: [Discuss] Apache Kylin Component Owner Plan

I would like to take the ownership of "BI Integration", or make it easier as "Integration" 2018-02-02 10:39 GMT+08:00 ShaoFeng Shi : > Hello, Kylin community, > > In the past, we don't have a clear rule on Kylin each component's > ownership, which caused many external

Re: [Discuss] Apache Kylin Component Owner Plan

Cool, thanks kaisen and others! I see there are many issues related to the "count distinct" and global dictionary; The function is across multiple components like job, query, metadata, web, etc. Top-N is also another case. So I propose to add independent components called "Measure - Count

Re: [Discuss] Apache Kylin Component Owner Plan

I would like to take the ownership of "Spark engine" components. I also could be a backup owner for "Job Engine" components. In this year，I and Dayue will contribute and take over "Storage-Druid" components. -- Sent from: http://apache-kylin.74782.x6.nabble.com/

Re: [Discuss] Apache Kylin Component Owner Plan

+1 I would like to take the ownership in " Web " and " REST Service " part. Thanks! Zhixiong Chen On 03/02/2018, 8:12 PM, "ShaoFeng Shi" wrote: Thanks guys; I have added liyang as one owner of "Metadata", Roger Shi as one owner of "Query engine"; How

Re: [Discuss] Apache Kylin Component Owner Plan

+1 I would like to take the ownership in " Web " and " REST Service " part. On 03/02/2018, 8:14 PM, "ShaoFeng Shi" wrote: I would like to take the ownership in "Documentation" and "Streaming" part. 2018-02-03 20:11 GMT+08:00 ShaoFeng Shi

Re: [Discuss] Apache Kylin Component Owner Plan

+1 No problem. I can continue taking the ownership of ODBC and JDBC components. Maybe I can also be one of the "RDBMS Source " owners, although it has no issues so far. Thanks, Dong Li 2018-02-03

Re: [Discuss] Apache Kylin Component Owner Plan

I would like to take the ownership in "Documentation" and "Streaming" part. 2018-02-03 20:11 GMT+08:00 ShaoFeng Shi : > Thanks guys; > > I have added liyang as one owner of "Metadata", Roger Shi as one owner of > "Query engine"; How about other committers' preference? > >

Re: [Discuss] Apache Kylin Component Owner Plan

Thanks guys; I have added liyang as one owner of "Metadata", Roger Shi as one owner of "Query engine"; How about other committers' preference? @Jianhua, would you like take the part of "Security" and "Web"? I see you have lots of patch in them. @Dong, will you take the ownership of ODBC and

Re: [Discuss] Apache Kylin Component Owner Plan

+1 I will set up the code coverage check rule for each PR when the Gitbox migration is done. 2018-02-02 15:34 GMT+08:00 hongbin ma : > +1 > > suggest to establish more solid rules on test coverage. I've seen lots > patches without proper tests > > On Fri, Feb 2, 2018 at

Re: [Discuss] Apache Kylin Component Owner Plan

+1 hejingke 邮箱：hejin...@gmail.com 签名由 网易邮箱大师 定制 在2018年02月02日 19:13，Roger Shi 写道： +1 I can take the owner of component "Query Engine". On 02/02/2018, 7:09 PM, "Li Yang" wrote:    +1        I can take the owner of component "Metadata" to offload Shaofeng.    And Roger is a

Re: [Discuss] Apache Kylin Component Owner Plan

+1. Thanks Shaofeng. It's more friendly for new contributors. -- Sent from: http://apache-kylin.74782.x6.nabble.com/

Re: [Discuss] Apache Kylin Component Owner Plan

+1 I can take the owner of component "Query Engine". On 02/02/2018, 7:09 PM, "Li Yang" wrote: +1 I can take the owner of component "Metadata" to offload Shaofeng. And Roger is a better person to own "Query Engine" than me. :-) Cheers Yang

Re: [Discuss] Apache Kylin Component Owner Plan

+1 I can take the owner of component "Metadata" to offload Shaofeng. And Roger is a better person to own "Query Engine" than me. :-) Cheers Yang On Fri, Feb 2, 2018 at 6:58 PM, kangkaisen wrote: > +1. Thanks Shaofeng. > > It's more friendly for new contributors. > > >

Re: [Discuss] Apache Kylin Component Owner Plan

+1 suggest to establish more solid rules on test coverage. I've seen lots patches without proper tests On Fri, Feb 2, 2018 at 2:57 PM, Jianhua Peng wrote: > +1 > > On 2018/02/02 02:39:38, ShaoFeng Shi wrote: > > Hello, Kylin community, > > > >

Re: [Discuss] Apache Kylin Component Owner Plan

+1 On 2018/02/02 02:39:38, ShaoFeng Shi wrote: > Hello, Kylin community, > > In the past, we don't have a clear rule on Kylin each component's > ownership, which caused many external patches be pending there as no > reviewer to pick up. > > Now we plan to make the

[Discuss] Apache Kylin Component Owner Plan

Hello, Kylin community, In the past, we don't have a clear rule on Kylin each component's ownership, which caused many external patches be pending there as no reviewer to pick up. Now we plan to make the process and responsibility more clear. The main idea is to identify the owners of each