Re: [Discuss] Apache Kylin Component Owner Plan

[Billy Liu]

+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 2:57 PM, Jianhua Peng  wrote:
>
>> +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 process and responsibility more clear. The main
>> > idea is to identify the owners of each Apache Kylin component.
>> >
>> > - Component owners will be listed in the description field on this Apache
>> > Kylin JIRA components page [1]. The owners are listed in the
>> 'Description'
>> > field rather than in the 'Component Lead' field because the latter only
>> > allows us to list one individual whereas it is encouraged that components
>> > have multiple owners.
>> >
>> > - Component owners are volunteers who are expert in their component
>> domain
>> > and may have an agenda on how they think their Apache Kylin component
>> > should evolve. The owner needs to be an Apache Kylin committer at this
>> > moment.
>> >
>> > - Owners will try and review patches that land within their component’s
>> > scope.
>> >
>> > - Owners can rotate, based on his aspiration.
>> >
>> > - When nominate or vote a new committer, the nominator needs to state
>> which
>> > component the candidate can be the owner.
>> >
>> > - If you're already an Apache Kylin committer and would like to be a
>> > volunteer as a component owner, just write to the dev list and we’ll sign
>> > you up.
>> >
>> > - If you think the component list need be updated (add, remove, rename,
>> > etc), write to the dev list and we’ll review that.
>> >
>> > Below is the component list with old component lead, which assumes to be
>> > updated soon.
>> >
>> > [1]
>> > https://issues.apache.org/jira/projects/KYLIN?
>> selectedItem=com.atlassian.jira.jira-projects-plugin:components-page
>> >
>> > Please comment on this plan; if no objection, we will run it for some
>> time
>> > to see the effect. Thanks for your inputs!
>> >
>> > And, thanks to Apache HBase community, from where I learned this.
>> >
>> > --
>> > Best regards,
>> >
>> > Shaofeng Shi 史少锋
>> >
>>
>
>
>
> --
> Regards,
>
> *Bin Mahone | 马洪宾*

Re: [VOTE] Migrate to gitbox

[Billy Liu]

Yes. For document update, PR will against the document branch.

2018-02-02 23:27 GMT+08:00 Jingke He :
> +1 does that mean we can also pr to website document ? hejingke 
> 邮箱：hejin...@gmail.com 签名由 网易邮箱大师 定制 在2018年02月02日 17:24，Jianhua Peng 写道： +1 On 
> 2018/02/01 02:37:20, Billy Liu  wrote: > Hi all, > > I'm 
> starting this vote to migrate Apache Kylin repository from git-wip > to 
> gitbox. Gitbox allows deeper integration with Github, enables > committers to 
> merge, close or edit pull request in Github directly. > > More features: > - 
> Easier for code review compared to the Review Board > - JIRA linking, which 
> will automatically link a PR with its corresponding JIRA > - Leverage Github 
> ecosystem, such as web hooks for PR monitor, Code > Static Analytics, 
> Coverage Report. > > For Kylin committers, you need to do link your Github 
> account with ASF > account through https://gitbox.apache.org/ > > [ ] +1, 
> Migrate Kylin repository to gitbox > [ ]  -1,  Keep the current git-wip no 
> change > > > Regards, > Billy Liu >

Re: [VOTE] Migrate to gitbox

[Jingke He]

+1 does that mean we can also pr to website document ? hejingke 
邮箱：hejin...@gmail.com 签名由 网易邮箱大师 定制 在2018年02月02日 17:24，Jianhua Peng 写道： +1 On 
2018/02/01 02:37:20, Billy Liu  wrote: > Hi all, > > I'm 
starting this vote to migrate Apache Kylin repository from git-wip > to gitbox. 
Gitbox allows deeper integration with Github, enables > committers to merge, 
close or edit pull request in Github directly. > > More features: > - Easier 
for code review compared to the Review Board > - JIRA linking, which will 
automatically link a PR with its corresponding JIRA > - Leverage Github 
ecosystem, such as web hooks for PR monitor, Code > Static Analytics, Coverage 
Report. > > For Kylin committers, you need to do link your Github account with 
ASF > account through https://gitbox.apache.org/ > > [ ] +1, Migrate Kylin 
repository to gitbox > [ ]  -1,  Keep the current git-wip no change > > > 
Regards, > Billy Liu >

Re: [Discuss] Apache Kylin Component Owner Plan

[Jingke He]

+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 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.    >    >    > --  
  > Sent from: http://apache-kylin.74782.x6.nabble.com/    >    

Re: 答复: Can't delete segment

[ShaoFeng Shi]

Thank you You Cheng; And if you want to contribute a patch, that is
welcomed!

2018-02-02 21:29 GMT+08:00 张 佑铖 :

>   1.  KYLIN-3228 has
> been created.
>   2.
>  *
>
> 
> 发件人: ShaoFeng Shi 
> 发送时间: 2018年2月2日 19:02
> 收件人: dev
> 主题: Re: Can't delete segment
>
> Hi yousheng, it looks be a bug; when deleting a job, it should remove the
> related segment. Could you please report a JIRA?
>
> Next time, you don't need to purge the cube; you can backup the metadata to
> disk, edit the cube json manually, and then restore it.
>
> 2018-02-02 18:29 GMT+08:00 张 佑铖 :
>
> > Hi kylin team,
> >
> > After a job been error, I click drop  instead of discard by mistake, I
> > can't find the job anywhere, but it still remain an empty segment in
> cube.
> > When I call restful request /{cubeName}/segs/{segmentName}   it returns
> > Cannot delete segment '' as its status is not READY. Discard the on-going
> > job for it
> > So it turn out to be a dilemma for, I can't build/refresh the segment,
> and
> > I can't delete either.
> > Finally I purge the cube...
> > I wonder if it is a bug or there is some solutions?
> >
> >
> > version 2.2.0
> >
> >
> > thanks
> >
> >
>
>
> --
> Best regards,
>
> Shaofeng Shi 史少锋
>



-- 
Best regards,

Shaofeng Shi 史少锋

答复: Can't delete segment

[张 佑铖]

  1.  KYLIN-3228 has been 
created.
  2.
 *


发件人: ShaoFeng Shi 
发送时间: 2018年2月2日 19:02
收件人: dev
主题: Re: Can't delete segment

Hi yousheng, it looks be a bug; when deleting a job, it should remove the
related segment. Could you please report a JIRA?

Next time, you don't need to purge the cube; you can backup the metadata to
disk, edit the cube json manually, and then restore it.

2018-02-02 18:29 GMT+08:00 张 佑铖 :

> Hi kylin team,
>
> After a job been error, I click drop  instead of discard by mistake, I
> can't find the job anywhere, but it still remain an empty segment in cube.
> When I call restful request /{cubeName}/segs/{segmentName}   it returns
> Cannot delete segment '' as its status is not READY. Discard the on-going
> job for it
> So it turn out to be a dilemma for, I can't build/refresh the segment, and
> I can't delete either.
> Finally I purge the cube...
> I wonder if it is a bug or there is some solutions?
>
>
> version 2.2.0
>
>
> thanks
>
>


--
Best regards,

Shaofeng Shi 史少锋

[jira] [Created] (KYLIN-3228) Should remove the related segment when deleting a job

[youcheng.zhang (JIRA)]

youcheng.zhang created KYLIN-3228:
-

 Summary: Should remove the related segment when deleting a job
 Key: KYLIN-3228
 URL: https://issues.apache.org/jira/browse/KYLIN-3228
 Project: Kylin
  Issue Type: Bug
  Components: Web 
Affects Versions: v2.2.0
Reporter: youcheng.zhang
Assignee: Zhixiong Chen


When delete error job in the web page, kylin doesn't  delete the relative 
segment, and the segment remain with status not ready, you can't delete it or 
refresh it either.

Even after use StorageCleanupJob, the segment still remains.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [Discuss] Apache Kylin Component Owner Plan

[kangkaisen]

+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

[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 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.
>
>
> --
> Sent from: http://apache-kylin.74782.x6.nabble.com/
>

Re: [Discuss] Apache Kylin Component Owner Plan

[Li Yang]

+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.
>
>
> --
> Sent from: http://apache-kylin.74782.x6.nabble.com/
>

Re: Can't delete segment

[ShaoFeng Shi]

Hi yousheng, it looks be a bug; when deleting a job, it should remove the
related segment. Could you please report a JIRA?

Next time, you don't need to purge the cube; you can backup the metadata to
disk, edit the cube json manually, and then restore it.

2018-02-02 18:29 GMT+08:00 张 佑铖 :

> Hi kylin team,
>
> After a job been error, I click drop  instead of discard by mistake, I
> can't find the job anywhere, but it still remain an empty segment in cube.
> When I call restful request /{cubeName}/segs/{segmentName}   it returns
> Cannot delete segment '' as its status is not READY. Discard the on-going
> job for it
> So it turn out to be a dilemma for, I can't build/refresh the segment, and
> I can't delete either.
> Finally I purge the cube...
> I wonder if it is a bug or there is some solutions?
>
>
> version 2.2.0
>
>
> thanks
>
>


-- 
Best regards,

Shaofeng Shi 史少锋

Can't delete segment

[张 佑铖]

Hi kylin team,

After a job been error, I click drop  instead of discard by mistake, I can't 
find the job anywhere, but it still remain an empty segment in cube.
When I call restful request /{cubeName}/segs/{segmentName}   it returns  Cannot 
delete segment '' as its status is not READY. Discard the on-going job for it
So it turn out to be a dilemma for, I can't build/refresh the segment, and I 
can't delete either.
Finally I purge the cube...
I wonder if it is a bug or there is some solutions?


version 2.2.0


thanks

Re: Welcome new Apache Kylin committer: Jianhua Peng

[kangkaisen]

Welcome Jianhua! 


--
Sent from: http://apache-kylin.74782.x6.nabble.com/

Re: [Discuss] Patch +1 Policy

[kangkaisen]

+1. Thanks Shaofeng.

It's great. Code review is necessary.

--
Sent from: http://apache-kylin.74782.x6.nabble.com/

Re: [Discuss] Patch +1 Policy

[ShaoFeng Shi]

Hi Jianhua,

Thanks for your suggestion.
In another thread, Billy is proposing to use apache gitbox to host Kylin
repository. After that, we may switch to GitHub PR for review and merge. If
so, I think the review board is no longer recommended.


2018-02-02 17:20 GMT+08:00 ShaoFeng Shi :

> Billy, this is an open discussion; A vote usually happens after the
> discussion. I'm not sure whether it is needed if all members are okay with
> it.
>
> 2018-02-02 14:56 GMT+08:00 Jianhua Peng :
>
>> +1
>>
>> On 2018/02/02 03:10:32, ShaoFeng Shi  wrote:
>> > Hello, Apache Kylin community,
>> >
>> > This is another proposal follows the "Component Owner" proposal;
>> >
>> > The below policy is a suggested policy rather than a hard requirement.
>> >
>> > Apache Kylin is made of components. Components have one or more OWNERs.
>> See
>> > the 'Description' field on the components JIRA page for who the current
>> > owners are by component.
>> >
>> > Patches that fit within the scope of a single component require, at
>> least,
>> > a +1 by one of the component’s owners before commit. If owners are
>> absent —
>> > busy or otherwise — two +1s by non-owners but committers will suffice.
>> >
>> > Patches that span components need at least two +1s before they can be
>> > committed, preferably +1s by owners of components touched by the
>> > x-component patch.
>> >
>> > Any -1 on a patch by anyone vetoes a patch; it cannot be committed until
>> > the justification for the -1 is addressed.
>> >
>> > Please review this policy and share your comments; If no objection, we
>> will
>> > update it to Kylin's development process and enforce it in the future.
>> > Thanks!
>> >
>> > --
>> > Best regards,
>> >
>> > Shaofeng Shi 史少锋
>> >
>>
>
>
>
> --
> Best regards,
>
> Shaofeng Shi 史少锋
>
>


-- 
Best regards,

Shaofeng Shi 史少锋

[jira] [Created] (KYLIN-3227) Automatically remove the blank at the end of lines in properties files

[Guangyao Li (JIRA)]

Guangyao Li created KYLIN-3227:
--

 Summary: Automatically remove the blank at the end of lines in 
properties files
 Key: KYLIN-3227
 URL: https://issues.apache.org/jira/browse/KYLIN-3227
 Project: Kylin
  Issue Type: Bug
  Components: Environment 
Affects Versions: v2.2.0
Reporter: Guangyao Li
Assignee: Wang Cheng
 Fix For: v2.3.0


In the 'kylin.properties' file:

eg: kap.storage.columnar.spark-conf.spark.executor.instances=1 

There is a blank space bebind "1"

The Kylin will startup failure.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (KYLIN-3226) When user logs in with only query permission, 'N/A' is displayed in the cube's action list.

[Peng Xing (JIRA)]

Peng Xing created KYLIN-3226:


 Summary: When user logs in with only query permission, 'N/A' is 
displayed in the cube's action list.
 Key: KYLIN-3226
 URL: https://issues.apache.org/jira/browse/KYLIN-3226
 Project: Kylin
  Issue Type: Bug
  Components: Web 
Affects Versions: v2.3.0
Reporter: Peng Xing
Assignee: Peng Xing
 Attachments: NA_action.png, only_query_permission.png

1. Only give the 'QUERY' permission of project 'learn_kylin' for user 'xp', 
refer to  !only_query_permission.png! 
2. When user 'xp' logins in, 'N/A' is displayed in the cube's action list, 
refer to  !NA_action.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Migrate to gitbox

[Jianhua Peng]

+1

On 2018/02/01 02:37:20, Billy Liu  wrote: 
> Hi all,
> 
> I'm starting this vote to migrate Apache Kylin repository from git-wip
> to gitbox. Gitbox allows deeper integration with Github, enables
> committers to merge, close or edit pull request in Github directly.
> 
> More features:
> - Easier for code review compared to the Review Board
> - JIRA linking, which will automatically link a PR with its corresponding JIRA
> - Leverage Github ecosystem, such as web hooks for PR monitor, Code
> Static Analytics, Coverage Report.
> 
> For Kylin committers, you need to do link your Github account with ASF
> account through https://gitbox.apache.org/
> 
> [ ] +1, Migrate Kylin repository to gitbox
> [ ]  -1,  Keep the current git-wip no change
> 
> 
> Regards,
> Billy Liu
> 

Re:[VOTE] Migrate to gitbox

[Dayue Gao]

+1 binding

Regards,
Dayue Gao


At 2018-02-01 10:37:20, "Billy Liu"  wrote:
>Hi all,
>
>I'm starting this vote to migrate Apache Kylin repository from git-wip
>to gitbox. Gitbox allows deeper integration with Github, enables
>committers to merge, close or edit pull request in Github directly.
>
>More features:
>- Easier for code review compared to the Review Board
>- JIRA linking, which will automatically link a PR with its corresponding JIRA
>- Leverage Github ecosystem, such as web hooks for PR monitor, Code
>Static Analytics, Coverage Report.
>
>For Kylin committers, you need to do link your Github account with ASF
>account through https://gitbox.apache.org/
>
>[ ] +1, Migrate Kylin repository to gitbox
>[ ]  -1,  Keep the current git-wip no change
>
>
>Regards,
>Billy Liu

Re: [Discuss] Patch +1 Policy

[ShaoFeng Shi]

Billy, this is an open discussion; A vote usually happens after the
discussion. I'm not sure whether it is needed if all members are okay with
it.

2018-02-02 14:56 GMT+08:00 Jianhua Peng :

> +1
>
> On 2018/02/02 03:10:32, ShaoFeng Shi  wrote:
> > Hello, Apache Kylin community,
> >
> > This is another proposal follows the "Component Owner" proposal;
> >
> > The below policy is a suggested policy rather than a hard requirement.
> >
> > Apache Kylin is made of components. Components have one or more OWNERs.
> See
> > the 'Description' field on the components JIRA page for who the current
> > owners are by component.
> >
> > Patches that fit within the scope of a single component require, at
> least,
> > a +1 by one of the component’s owners before commit. If owners are
> absent —
> > busy or otherwise — two +1s by non-owners but committers will suffice.
> >
> > Patches that span components need at least two +1s before they can be
> > committed, preferably +1s by owners of components touched by the
> > x-component patch.
> >
> > Any -1 on a patch by anyone vetoes a patch; it cannot be committed until
> > the justification for the -1 is addressed.
> >
> > Please review this policy and share your comments; If no objection, we
> will
> > update it to Kylin's development process and enforce it in the future.
> > Thanks!
> >
> > --
> > Best regards,
> >
> > Shaofeng Shi 史少锋
> >
>



-- 
Best regards,

Shaofeng Shi 史少锋

Re: [Discuss] Patch +1 Policy

[Jianhua Peng]

Hi shaofeng,

We can also do the following step:
1. submit issue in https://issues.apache.org;
2. related a review request to https://reviews.apache.org/dashboard;
3. The committer can patch +1 policy in review request;
4. The committer can review patch of issue in review request. 
example:
https://issues.apache.org/jira/browse/RANGER-1797


On 2018/02/02 03:10:32, ShaoFeng Shi  wrote: 
> Hello, Apache Kylin community,
> 
> This is another proposal follows the "Component Owner" proposal;
> 
> The below policy is a suggested policy rather than a hard requirement.
> 
> Apache Kylin is made of components. Components have one or more OWNERs. See
> the 'Description' field on the components JIRA page for who the current
> owners are by component.
> 
> Patches that fit within the scope of a single component require, at least,
> a +1 by one of the component’s owners before commit. If owners are absent 
> —
> busy or otherwise — two +1s by non-owners but committers will suffice.
> 
> Patches that span components need at least two +1s before they can be
> committed, preferably +1s by owners of components touched by the
> x-component patch.
> 
> Any -1 on a patch by anyone vetoes a patch; it cannot be committed until
> the justification for the -1 is addressed.
> 
> Please review this policy and share your comments; If no objection, we will
> update it to Kylin's development process and enforce it in the future.
> Thanks!
> 
> -- 
> Best regards,
> 
> Shaofeng Shi 史少锋
> 

Re: Welcome new Apache Kylin committer: Jianhua Peng

[Ted Yu]

Congratulations,  Jianhua !
 Original message From: Luke Han  Date: 
2/1/18  10:02 PM  (GMT-08:00) To: dev , user 
, Apache Kylin PMC  Subject: 
Welcome new Apache Kylin committer: Jianhua Peng 
I am very pleased to announce that the Project Management Committee(PMC) of 
Apache Kylin has asked Jianhua Peng to becomeApache Kylin committer, and he has 
already accepted.
Jianhua has already made many contributions to Kylin community, to answer 
others questions actively, submit patches for bug fixes and contribute to some 
features. We are so glad to have him to be our new committer.
Please join me to welcome Billy.
Luke Han
On behalf of the Apache Kylin PPMC

[jira] [Created] (KYLIN-3225) java.lang.ClassNotFoundException: org.apache.kylin.jdbc.Driver

[Bowen Yang (JIRA)]

Bowen Yang created KYLIN-3225:
-

 Summary: java.lang.ClassNotFoundException: 
org.apache.kylin.jdbc.Driver
 Key: KYLIN-3225
 URL: https://issues.apache.org/jira/browse/KYLIN-3225
 Project: Kylin
  Issue Type: Bug
  Components: Driver - JDBC
Affects Versions: v2.2.0
Reporter: Bowen Yang
Assignee: Dong Li
 Attachments: KylinClient.java, 
WeChatWorkScreenshot_9a071c7d-18b3-445a-8f99-1bed111250b3.png, 
WeChatWorkScreenshot_de991bc7-7635-49ab-a53b-08899cd7ef4b.png, pom.xml

Hi guys,

I am using jdbc to connect kylin which version is 2.2.0 to analyze something, 
but I got "java.lang.ClassNotFoundException: org.apache.kylin.jdbc.Driver" 
exception.

I tried 1.5.3 and 1.6.0 version, but this exception still happened.

Is it a bug in the kylin jdbc driver? The attachments are my pom, java code and 
screenshots, please help to see this issue. Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)