[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150094#comment-16150094 ] qiumingming commented on KYLIN-2720: OK, I got it. Thank you very much! So you can close this issue. > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148686#comment-16148686 ] qiumingming commented on KYLIN-2720: Okay, I see. But I'm also confused. Is that means I will not see any some other tables in the web UI that I owned cubes do not dependent to. I have not upgraded to kylin 2.1, so I want to know it. As you can see, my patch did nothing about ACL grant or revoke, it just control tables that being displayed in the web UI. So user will not see tables he can not query to in the web UI. Otherwise, user will be confused : why display tables that I can not query? > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143334#comment-16143334 ] qiumingming commented on KYLIN-2720: Hi [~Shaofengshi], What's going on? Many days have passed. > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16131795#comment-16131795 ] qiumingming edited comment on KYLIN-2720 at 8/18/17 12:38 PM: -- Hi [~Shaofengshi], Is there any status update? Should I start to make a new version patch for this issue? was (Author: qmm): Hi [~Shaofengshi], Is there any status update? Can I start to make a new version patch for this issue? > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16131795#comment-16131795 ] qiumingming edited comment on KYLIN-2720 at 8/18/17 6:32 AM: - Hi [~Shaofengshi], Is there any status update? Can I start to make a new version patch for this issue? was (Author: qmm): Is there any status update? Can I start to make a new version patch for this issue? > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16131795#comment-16131795 ] qiumingming commented on KYLIN-2720: Is there any status update? Can I start to make a new version patch for this issue? > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (KYLIN-2646) Project level query authorization
[ https://issues.apache.org/jira/browse/KYLIN-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2646: --- Comment: was deleted (was: OK, I will follow this issue.) > Project level query authorization > - > > Key: KYLIN-2646 > URL: https://issues.apache.org/jira/browse/KYLIN-2646 > Project: Kylin > Issue Type: Improvement >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v2.1.0 > > > As we introduced ad-hoc queries in > https://issues.apache.org/jira/browse/KYLIN-2515, we'll need to adjust query > authorization as follows: > Query authorization is encouraged to be set as project level. If someone is > assigned READ permission on project, then he has access to query all tables > in the project, regardless thru adhoc or cubes > If a user has READ permission on cubes but no READ permission on project. He > can only issue queries only if the query can be satisfied by those cubes he > has READ permission. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110729#comment-16110729 ] qiumingming commented on KYLIN-2720: OK, I will follow this issue. > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Fix For: v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2646) Project level query authorization
[ https://issues.apache.org/jira/browse/KYLIN-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110728#comment-16110728 ] qiumingming commented on KYLIN-2646: OK, I will follow this issue. > Project level query authorization > - > > Key: KYLIN-2646 > URL: https://issues.apache.org/jira/browse/KYLIN-2646 > Project: Kylin > Issue Type: Improvement >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v2.1.0 > > > As we introduced ad-hoc queries in > https://issues.apache.org/jira/browse/KYLIN-2515, we'll need to adjust query > authorization as follows: > Query authorization is encouraged to be set as project level. If someone is > assigned READ permission on project, then he has access to query all tables > in the project, regardless thru adhoc or cubes > If a user has READ permission on cubes but no READ permission on project. He > can only issue queries only if the query can be satisfied by those cubes he > has READ permission. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16107533#comment-16107533 ] qiumingming commented on KYLIN-2720: (y) > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Fix For: v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming reassigned KYLIN-2720: -- Assignee: qiumingming (was: Shaofeng SHI) > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Fix For: Future > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming reassigned KYLIN-2720: -- Assignee: Shaofeng SHI (was: qiumingming) > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: Shaofeng SHI > Fix For: Future > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[
https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095958#comment-16095958
]
qiumingming commented on KYLIN-2720:
I see. And is there any other problems? This issue's status still is
{color:#f6c342}IN PROGRESS{color}.
> Should not allow user to access to all tables' metadata of a project
>
>
> Key: KYLIN-2720
> URL: https://issues.apache.org/jira/browse/KYLIN-2720
> Project: Kylin
> Issue Type: Improvement
>Reporter: qiumingming
>Assignee: Shaofeng SHI
> Fix For: Future
>
> Attachments: KYLIN-2720.patch
>
>
> Currently, user can access to all tables and columns metadata of a specific
> project as long as he can access to this project, which is not reasonable.
> User should just allow to access to tables that he owned cubes dependent to.
> However, user can see some other tables in the web UI in current version.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[
https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095750#comment-16095750
]
qiumingming commented on KYLIN-2720:
I see. There is a mistake in the patch: @Qualifier("cubeService") should be
@Qualifier("cubeMgmtService"). I run well in kylin 1.5. But there are some code
differences between master-branch and 1.5. I am sorry for this. A new version
patch has been attached.
> Should not allow user to access to all tables' metadata of a project
>
>
> Key: KYLIN-2720
> URL: https://issues.apache.org/jira/browse/KYLIN-2720
> Project: Kylin
> Issue Type: Improvement
>Reporter: qiumingming
>Assignee: qiumingming
> Fix For: v2.0.0, v2.1.0
>
> Attachments: KYLIN-2720.patch
>
>
> Currently, user can access to all tables and columns metadata of a specific
> project as long as he can access to this project, which is not reasonable.
> User should just allow to access to tables that he owned cubes dependent to.
> However, user can see some other tables in the web UI in current version.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Attachment: KYLIN-2720.patch > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Attachment: (was: KYLIN-2720.patch) > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095694#comment-16095694 ] qiumingming edited comment on KYLIN-2720 at 7/21/17 2:46 AM: - Hi [~Shaofengshi], What's going on about this issue. Many days have passed. was (Author: qmm): Hi [~Shaofeng SHI], What's going on about this issue. Many days have passed. > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095694#comment-16095694 ] qiumingming edited comment on KYLIN-2720 at 7/21/17 2:40 AM: - Hi Shaofeng SHI , What's going on about this issue. Many days have passed. was (Author: qmm): Hi Shaofeng SHI , What's going on about this issue. Many days have passed. > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095694#comment-16095694 ] qiumingming edited comment on KYLIN-2720 at 7/21/17 2:46 AM: - Hi [~Shaofeng SHI], What's going on about this issue. Many days have passed. was (Author: qmm): Hi Shaofeng SHI, What's going on about this issue. Many days have passed. > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095694#comment-16095694 ] qiumingming edited comment on KYLIN-2720 at 7/21/17 2:41 AM: - Hi Shaofeng SHI, What's going on about this issue. Many days have passed. was (Author: qmm): Hi Shaofeng SHI, What's going on about this issue. Many days have passed. > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095694#comment-16095694 ] qiumingming edited comment on KYLIN-2720 at 7/21/17 2:41 AM: - Hi Shaofeng SHI, What's going on about this issue. Many days have passed. was (Author: qmm): Hi Shaofeng SHI , What's going on about this issue. Many days have passed. > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095694#comment-16095694 ] qiumingming commented on KYLIN-2720: Hi Shaofeng SHI , What's going on about this issue. Many days have passed. > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089423#comment-16089423 ] qiumingming commented on KYLIN-2720: A new version patch has been attached. > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Attachment: KYLIN-2720.patch > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Attachment: (was: KYLIN-2720.patch) > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Attachment: KYLIN-2720.patch > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Attachment: (was: KYLIN-2720.patch) > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089342#comment-16089342 ] qiumingming commented on KYLIN-2720: Thanks for your reminder. In my patch there are two REST interfaces will be impacted:1.getMetadata in QueryController; 2. getTableDesc in TableController. The latter will impact an user from creating new model/cube while the former will not. When an user clicks the "Insight" bar in the web UI the former interface will be called. So just allow user to access to tables that he owned cubes dependent to in this situation will be great. Because user will not see tables he can not query in the web UI. I can contribute a new patch and remove the modification of the TableService for it have an negative impact when creating new model/cube. The modification of the QueryService will be kept for it have no negative impact. > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Summary: Should not allow user to access to all tables' metadata of a project (was: Should not allow user to access to all table metadata of a project) > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all table metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Summary: Should not allow user to access to all table metadata of a project (was: Should not allow user to access to all tables of a project) > Should not allow user to access to all table metadata of a project > -- > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all tables of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Description: Currently, user can access to all tables and columns metadata of a specific project as long as he can access to this project, which is not reasonable. User should just allow to access to tables that he owned cubes dependent to. However, user can see some other tables in the web UI in current version. (was: Currently, user can access to all tables and columns metadata of a specific project as long as he can access to this project, which is not reasonable. User should just allow to access to tables that he owned cubes dependent to.) > Should not allow user to access to all tables of a project > -- > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all tables of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Attachment: KYLIN-2720.patch > Should not allow user to access to all tables of a project > -- > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all tables of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Attachment: KYLIN-2720.patch > Should not allow user to access to all tables of a project > -- > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2720) Should not allow user to access to all tables of a project
qiumingming created KYLIN-2720: -- Summary: Should not allow user to access to all tables of a project Key: KYLIN-2720 URL: https://issues.apache.org/jira/browse/KYLIN-2720 Project: Kylin Issue Type: Improvement Reporter: qiumingming Fix For: v2.1.0, v2.0.0 Currently, user can access to all tables and columns metadata of a specific project as long as he can access to this project, which is not reasonable. User should just allow to access to tables that he owned cubes dependent to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081975#comment-16081975 ] qiumingming commented on KYLIN-2720: If a user can access to all tables of a project, he may get some information that he should not allow to know. Besides, it will also make user confused that he can not query some tables he saw in the web UI. > Should not allow user to access to all tables of a project > -- > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081970#comment-16081970 ] qiumingming commented on KYLIN-2720: I contribute a patch for this issue. > Should not allow user to access to all tables of a project > -- > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (KYLIN-2699) Tomcat LinkageError for curator-client jar file conflict
[ https://issues.apache.org/jira/browse/KYLIN-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming reopened KYLIN-2699: > Tomcat LinkageError for curator-client jar file conflict > > > Key: KYLIN-2699 > URL: https://issues.apache.org/jira/browse/KYLIN-2699 > Project: Kylin > Issue Type: Bug > Components: Job Engine, Web >Affects Versions: v2.0.0 >Reporter: qiumingming >Assignee: Dong Li > Attachments: KYLIN-2699.patch > > > Exception: java.lang.LinkageError: loader constraint violation: loader > (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading > for a different type with name "org/apache/curator/RetryPolicy" > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at > org.apache.curator.CuratorZookeeperClient.(CuratorZookeeperClient.java:97) > at > org.apache.curator.framework.imps.CuratorFrameworkImpl.(CuratorFrameworkImpl.java:108) > at > org.apache.curator.framework.CuratorFrameworkFactory$Builder.build(CuratorFrameworkFactory.java:124) > at > org.apache.kylin.storage.hbase.util.ZookeeperJobLock.lock(ZookeeperJobLock.java:70) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler.init(DefaultScheduler.java:208) > at org.apache.kylin.rest.service.JobService$1.run(JobService.java:116) > at java.lang.Thread.run(Thread.java:745) > This exception will make kylin job engine does not work. And I found it > occured because in the kylin/WEB-INF/lib contains the > curator-client-2.7.1.jar which make some conflicts. In general, the HBase and > Hadoop cluster always contain their own curator-client jar files. So there is > no need to include the curator-client jar file in kylin/WEB-INF/lib. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2699) Tomcat LinkageError for curator-client jar file conflict
[ https://issues.apache.org/jira/browse/KYLIN-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074410#comment-16074410 ] qiumingming edited comment on KYLIN-2699 at 7/5/17 8:27 AM: Actually, the source code branch I used already contained KYLIN-2428 commit. And I look through the changed files of this commit, I found it did not contain the content my patch refered. In KYLIN-2428 did not set curator-client's scope to provided explicitly in pom.xml file. And when I compiled with maven, curator-client-2.7.1.jar will be packaged into kylin.war. At first, I also think it is not necessary to do so, becasue curator-framework's scope has been set to provided, and curator-framework contains curator-client in it's dependencies list so maven would also exclude curator-client when make a package. However, it did not work unless set curator-client's scope to provided explicitly. Finally, I figure out why it did not work: maven's version make a difference. In old versions(like maven 3.0.5) it would contain curator-client when packaged. But when I compiled by Maven 3.3.9 it works well. In conclusion, I think it is better to set curator-client's scope to provided in order to take care of different maven versions. was (Author: qmm): Actually, the source code branch I used already contained KYLIN-2428 commit. And I look through the changed files of this commit, I found it did not contain the content my patch refered. In KYLIN-242 did not set curator-client's scope to provided explicitly in pom.xml file. And when I compiled with maven, curator-client-2.7.1.jar will be packaged into kylin.war. At first, I also think it is not necessary to do so, becasue curator-framework's scope has been set to provided, and curator-framework contains curator-client in it's dependencies list so maven would also exclude curator-client when make a package. However, it did not work unless set curator-client's scope to provided explicitly. Finally, I figure out why it did not work: maven's version make a difference. In old versions(like maven 3.0.5) it would contain curator-client when packaged. But when I compiled by Maven 3.3.9 it works well. In conclusion, I think it is better to set curator-client's scope to provided in order to take care of different maven versions. > Tomcat LinkageError for curator-client jar file conflict > > > Key: KYLIN-2699 > URL: https://issues.apache.org/jira/browse/KYLIN-2699 > Project: Kylin > Issue Type: Bug > Components: Job Engine, Web >Affects Versions: v2.0.0 >Reporter: qiumingming >Assignee: Dong Li > Attachments: KYLIN-2699.patch > > > Exception: java.lang.LinkageError: loader constraint violation: loader > (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading > for a different type with name "org/apache/curator/RetryPolicy" > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at > org.apache.curator.CuratorZookeeperClient.(CuratorZookeeperClient.java:97) > at > org.apache.curator.framework.imps.CuratorFrameworkImpl.(CuratorFrameworkImpl.java:108) > at > org.apache.curator.framework.CuratorFrameworkFactory$Builder.build(CuratorFrameworkFactory.java:124) > at > org.apache.kylin.storage.hbase.util.ZookeeperJobLock.lock(ZookeeperJobLock.java:70) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler.init(DefaultScheduler.java:208) > at org.apache.kylin.rest.service.JobService$1.run(JobService.java:116) > at java.lang.Thread.run(Thread.java:745) > This exception will make kylin job engine does not work. And I found it > occured because in the kylin/WEB-INF/lib contains the > curator-client-2.7.1.jar which make some conflicts. In general, the HBase and > Hadoop cluster always contain their own curator-client jar files. So there is > no need to include the curator-client jar file in kylin/WEB-INF/lib. -- This message was sent by Atlassian JIRA
[jira] [Commented] (KYLIN-2699) Tomcat LinkageError for curator-client jar file conflict
[ https://issues.apache.org/jira/browse/KYLIN-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074410#comment-16074410 ] qiumingming commented on KYLIN-2699: Actually, the source code branch I used already contained KYLIN-2428 commit. And I look through the changed files of this commit, I found it did not contain the content my patch refered. In KYLIN-242 did not set curator-client's scope to provided explicitly in pom.xml file. And when I compiled with maven, curator-client-2.7.1.jar will be packaged into kylin.war. At first, I also think it is not necessary to do so, becasue curator-framework's scope has been set to provided, and curator-framework contains curator-client in it's dependencies list so maven would also exclude curator-client when make a package. However, it did not work unless set curator-client's scope to provided explicitly. Finally, I figure out why it did not work: maven's version make a difference. In old versions(like maven 3.0.5) it would contain curator-client when packaged. But when I compiled by Maven 3.3.9 it works well. In conclusion, I think it is better to set curator-client's scope to provided in order to take care of different maven versions. > Tomcat LinkageError for curator-client jar file conflict > > > Key: KYLIN-2699 > URL: https://issues.apache.org/jira/browse/KYLIN-2699 > Project: Kylin > Issue Type: Bug > Components: Job Engine, Web >Affects Versions: v2.0.0 >Reporter: qiumingming >Assignee: Dong Li > Attachments: KYLIN-2699.patch > > > Exception: java.lang.LinkageError: loader constraint violation: loader > (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading > for a different type with name "org/apache/curator/RetryPolicy" > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at > org.apache.curator.CuratorZookeeperClient.(CuratorZookeeperClient.java:97) > at > org.apache.curator.framework.imps.CuratorFrameworkImpl.(CuratorFrameworkImpl.java:108) > at > org.apache.curator.framework.CuratorFrameworkFactory$Builder.build(CuratorFrameworkFactory.java:124) > at > org.apache.kylin.storage.hbase.util.ZookeeperJobLock.lock(ZookeeperJobLock.java:70) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler.init(DefaultScheduler.java:208) > at org.apache.kylin.rest.service.JobService$1.run(JobService.java:116) > at java.lang.Thread.run(Thread.java:745) > This exception will make kylin job engine does not work. And I found it > occured because in the kylin/WEB-INF/lib contains the > curator-client-2.7.1.jar which make some conflicts. In general, the HBase and > Hadoop cluster always contain their own curator-client jar files. So there is > no need to include the curator-client jar file in kylin/WEB-INF/lib. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2700) Should allow user to override Kafka conf in cube level
[ https://issues.apache.org/jira/browse/KYLIN-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2700: --- Affects Version/s: v2.0.0 Fix Version/s: (was: v2.1.0) > Should allow user to override Kafka conf in cube level > -- > > Key: KYLIN-2700 > URL: https://issues.apache.org/jira/browse/KYLIN-2700 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.0.0 >Reporter: qiumingming > Attachments: KYLIN-2700.patch > > > Currently, user can not override Kafka conf in cube level. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2700) Should allow user to override Kafka conf in cube level
[ https://issues.apache.org/jira/browse/KYLIN-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16069870#comment-16069870 ] qiumingming commented on KYLIN-2700: I contribute a patch for this issue. > Should allow user to override Kafka conf in cube level > -- > > Key: KYLIN-2700 > URL: https://issues.apache.org/jira/browse/KYLIN-2700 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Attachments: KYLIN-2700.patch > > > Currently, user can not override Kafka conf in cube level. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2700) Should allow user to override Kafka conf in cube level
[ https://issues.apache.org/jira/browse/KYLIN-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2700: --- Attachment: KYLIN-2700.patch > Should allow user to override Kafka conf in cube level > -- > > Key: KYLIN-2700 > URL: https://issues.apache.org/jira/browse/KYLIN-2700 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Attachments: KYLIN-2700.patch > > > Currently, user can not override Kafka conf in cube level. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2700) Should allow user to override Kafka conf in cube level
qiumingming created KYLIN-2700: -- Summary: Should allow user to override Kafka conf in cube level Key: KYLIN-2700 URL: https://issues.apache.org/jira/browse/KYLIN-2700 Project: Kylin Issue Type: Improvement Reporter: qiumingming Currently, user can not override Kafka conf in cube level. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2699) Tomcat LinkageError for curator-client jar file conflict
[ https://issues.apache.org/jira/browse/KYLIN-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2699: --- Attachment: KYLIN-2699.patch I contribute a patch for this issue. > Tomcat LinkageError for curator-client jar file conflict > > > Key: KYLIN-2699 > URL: https://issues.apache.org/jira/browse/KYLIN-2699 > Project: Kylin > Issue Type: Bug > Components: Job Engine, Web >Affects Versions: v2.0.0 >Reporter: qiumingming >Assignee: Dong Li > Attachments: KYLIN-2699.patch > > > Exception: java.lang.LinkageError: loader constraint violation: loader > (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading > for a different type with name "org/apache/curator/RetryPolicy" > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at > org.apache.curator.CuratorZookeeperClient.(CuratorZookeeperClient.java:97) > at > org.apache.curator.framework.imps.CuratorFrameworkImpl.(CuratorFrameworkImpl.java:108) > at > org.apache.curator.framework.CuratorFrameworkFactory$Builder.build(CuratorFrameworkFactory.java:124) > at > org.apache.kylin.storage.hbase.util.ZookeeperJobLock.lock(ZookeeperJobLock.java:70) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler.init(DefaultScheduler.java:208) > at org.apache.kylin.rest.service.JobService$1.run(JobService.java:116) > at java.lang.Thread.run(Thread.java:745) > This exception will make kylin job engine does not work. And I found it > occured because in the kylin/WEB-INF/lib contains the > curator-client-2.7.1.jar which make some conflicts. In general, the HBase and > Hadoop cluster always contain their own curator-client jar files. So there is > no need to include the curator-client jar file in kylin/WEB-INF/lib. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2699) Tomcat LinkageError for curator-client jar file conflict
qiumingming created KYLIN-2699: -- Summary: Tomcat LinkageError for curator-client jar file conflict Key: KYLIN-2699 URL: https://issues.apache.org/jira/browse/KYLIN-2699 Project: Kylin Issue Type: Bug Components: Job Engine, Web Affects Versions: v2.0.0 Reporter: qiumingming Assignee: Dong Li Exception: java.lang.LinkageError: loader constraint violation: loader (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading for a different type with name "org/apache/curator/RetryPolicy" at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) at java.net.URLClassLoader.access$100(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:368) at java.net.URLClassLoader$1.run(URLClassLoader.java:362) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:361) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.apache.curator.CuratorZookeeperClient.(CuratorZookeeperClient.java:97) at org.apache.curator.framework.imps.CuratorFrameworkImpl.(CuratorFrameworkImpl.java:108) at org.apache.curator.framework.CuratorFrameworkFactory$Builder.build(CuratorFrameworkFactory.java:124) at org.apache.kylin.storage.hbase.util.ZookeeperJobLock.lock(ZookeeperJobLock.java:70) at org.apache.kylin.job.impl.threadpool.DefaultScheduler.init(DefaultScheduler.java:208) at org.apache.kylin.rest.service.JobService$1.run(JobService.java:116) at java.lang.Thread.run(Thread.java:745) This exception will make kylin job engine does not work. And I found it occured because in the kylin/WEB-INF/lib contains the curator-client-2.7.1.jar which make some conflicts. In general, the HBase and Hadoop cluster always contain their own curator-client jar files. So there is no need to include the curator-client jar file in kylin/WEB-INF/lib. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2654) Kylin failed to build cube at 3rd step on Hadoop 2.6.0-cdh5.4.4 + jdk 1.8
[
https://issues.apache.org/jira/browse/KYLIN-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035029#comment-16035029
]
qiumingming commented on KYLIN-2654:
By the way, is there any specific configuration to make SelfDefineSortableKey
work, like register serializer for SelfDefineSortableKey explicitly. And Have
you modified the pom.xml in your test, like change some versions ?
> Kylin failed to build cube at 3rd step on Hadoop 2.6.0-cdh5.4.4 + jdk 1.8
> -
>
> Key: KYLIN-2654
> URL: https://issues.apache.org/jira/browse/KYLIN-2654
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v2.0.0
>Reporter: Shaofeng SHI
>Assignee: Dong Li
>
> From community user qiumingming:
> When I use kylin 2.0 to build cube, I got a error at Extract Fact Table
> Distinct Columns step, mr job failed. My Hadoop version is 2.6.0-cdh5.4.4.
> Below is my error info:
> {code}
> Error: java.io.IOException: Initialization of all the collectors failed.
> Error in last collector was :Cannot find serializer for
> org.apache.kylin.engine.mr.steps.SelfDefineSortableKey at
> org.apache.hadoop.mapred.MapTask.createSortingCollector(MapTask.java:423) at
> org.apache.hadoop.mapred.MapTask.access$100(MapTask.java:82) at
> org.apache.hadoop.mapred.MapTask$NewOutputCollector.(MapTask.java:718)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:790) at
> org.apache.hadoop.mapred.MapTask.run(MapTask.java:350) at
> org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163) at
> java.security.AccessController.doPrivileged(Native Method) at
> javax.security.auth.Subject.doAs(Subject.java:422) at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158) Caused by:
> java.io.IOException: Cannot find serializer for
> org.apache.kylin.engine.mr.steps.SelfDefineSortableKey at
> org.apache.hadoop.mapred.nativetask.NativeMapOutputCollectorDelegator.init(NativeMapOutputCollectorDelegator.java:147)
> at org.apache.hadoop.mapred.MapTask.createSortingCollector(MapTask.java:411)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KYLIN-2654) Kylin failed to build cube at 3rd step on Hadoop 2.6.0-cdh5.4.4 + jdk 1.8
[
https://issues.apache.org/jira/browse/KYLIN-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035017#comment-16035017
]
qiumingming commented on KYLIN-2654:
Yeah, I think so. Maybe my environment is so specific. And I solved this
problem by backing SelfDefineSortableKey to Text as old version done. I want to
know is this will involve any bug ? I am not very sure about that.
> Kylin failed to build cube at 3rd step on Hadoop 2.6.0-cdh5.4.4 + jdk 1.8
> -
>
> Key: KYLIN-2654
> URL: https://issues.apache.org/jira/browse/KYLIN-2654
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v2.0.0
>Reporter: Shaofeng SHI
>Assignee: Dong Li
>
> From community user qiumingming:
> When I use kylin 2.0 to build cube, I got a error at Extract Fact Table
> Distinct Columns step, mr job failed. My Hadoop version is 2.6.0-cdh5.4.4.
> Below is my error info:
> {code}
> Error: java.io.IOException: Initialization of all the collectors failed.
> Error in last collector was :Cannot find serializer for
> org.apache.kylin.engine.mr.steps.SelfDefineSortableKey at
> org.apache.hadoop.mapred.MapTask.createSortingCollector(MapTask.java:423) at
> org.apache.hadoop.mapred.MapTask.access$100(MapTask.java:82) at
> org.apache.hadoop.mapred.MapTask$NewOutputCollector.(MapTask.java:718)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:790) at
> org.apache.hadoop.mapred.MapTask.run(MapTask.java:350) at
> org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163) at
> java.security.AccessController.doPrivileged(Native Method) at
> javax.security.auth.Subject.doAs(Subject.java:422) at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158) Caused by:
> java.io.IOException: Cannot find serializer for
> org.apache.kylin.engine.mr.steps.SelfDefineSortableKey at
> org.apache.hadoop.mapred.nativetask.NativeMapOutputCollectorDelegator.init(NativeMapOutputCollectorDelegator.java:147)
> at org.apache.hadoop.mapred.MapTask.createSortingCollector(MapTask.java:411)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KYLIN-2654) Kylin failed to build cube at 3rd step on Hadoop 2.6
[
https://issues.apache.org/jira/browse/KYLIN-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16034354#comment-16034354
]
qiumingming commented on KYLIN-2654:
I modified the code of Extract Fact Table Distinct Columns step, just back
SelfDefineSortableKey to Text as old version done. Finally, it works. In my
understanding, using Text as the Map Output Key Class won't involve any error.
However, SelfDefineSortableKey can handle numeric type better and have a good
performance for it can sort digits in a right way. So, I am looking forward to
this problem can be solved in a elegant way!
> Kylin failed to build cube at 3rd step on Hadoop 2.6
>
>
> Key: KYLIN-2654
> URL: https://issues.apache.org/jira/browse/KYLIN-2654
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v2.0.0
>Reporter: Shaofeng SHI
>Assignee: Dong Li
>
> From community user qiumingming:
> When I use kylin 2.0 to build cube, I got a error at Extract Fact Table
> Distinct Columns step, mr job failed. My Hadoop version is 2.6.0-cdh5.4.4.
> Below is my error info:
> {code}
> Error: java.io.IOException: Initialization of all the collectors failed.
> Error in last collector was :Cannot find serializer for
> org.apache.kylin.engine.mr.steps.SelfDefineSortableKey at
> org.apache.hadoop.mapred.MapTask.createSortingCollector(MapTask.java:423) at
> org.apache.hadoop.mapred.MapTask.access$100(MapTask.java:82) at
> org.apache.hadoop.mapred.MapTask$NewOutputCollector.(MapTask.java:718)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:790) at
> org.apache.hadoop.mapred.MapTask.run(MapTask.java:350) at
> org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163) at
> java.security.AccessController.doPrivileged(Native Method) at
> javax.security.auth.Subject.doAs(Subject.java:422) at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158) Caused by:
> java.io.IOException: Cannot find serializer for
> org.apache.kylin.engine.mr.steps.SelfDefineSortableKey at
> org.apache.hadoop.mapred.nativetask.NativeMapOutputCollectorDelegator.init(NativeMapOutputCollectorDelegator.java:147)
> at org.apache.hadoop.mapred.MapTask.createSortingCollector(MapTask.java:411)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
