[jira] [Updated] (KYLIN-3158) Metadata broadcast should only retry failed node
[ https://issues.apache.org/jira/browse/KYLIN-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang updated KYLIN-3158: -- Description: In commit https://github.com/apache/kylin/commit/ecc01458c4ad361aaf863505884d51474a8fec9d, Kylin starts to retry failed metadata sync event, however it re-posts the failed event to all nodes. The retry SHOULD only apply to the failed node only. > Metadata broadcast should only retry failed node > > > Key: KYLIN-3158 > URL: https://issues.apache.org/jira/browse/KYLIN-3158 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > > In commit > https://github.com/apache/kylin/commit/ecc01458c4ad361aaf863505884d51474a8fec9d, > Kylin starts to retry failed metadata sync event, however it re-posts the > failed event to all nodes. The retry SHOULD only apply to the failed node > only. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-3158) Metadata broadcast should only retry failed node
liyang created KYLIN-3158: - Summary: Metadata broadcast should only retry failed node Key: KYLIN-3158 URL: https://issues.apache.org/jira/browse/KYLIN-3158 Project: Kylin Issue Type: Improvement Reporter: liyang Assignee: liyang -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3144) Adopt Collections.emptyList() for empty list values
[ https://issues.apache.org/jira/browse/KYLIN-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316128#comment-16316128 ] jiatao.tao commented on KYLIN-3144: --- Thanks. > Adopt Collections.emptyList() for empty list values > --- > > Key: KYLIN-3144 > URL: https://issues.apache.org/jira/browse/KYLIN-3144 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu >Assignee: jiatao.tao >Priority: Minor > > Use Collection.emptyList() for returning an empty list instead of returning > new ArrayList<>(). > The default constructor creates a buffer of size 10 for ArrayList . > Therefore, returning this static value saves some memory and lessens GC > pressure. > One candidate for replacement is in HybridService#listHybrids() -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2980) Remove getKey/Value setKey/Value from Kylin's Pair.
[ https://issues.apache.org/jira/browse/KYLIN-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316111#comment-16316111 ] jiatao.tao commented on KYLIN-2980: --- Here's the commit: https://github.com/apache/kylin/commit/4078c96eca5864b0397a9f402de52341a3fcff4c > Remove getKey/Value setKey/Value from Kylin's Pair. > --- > > Key: KYLIN-2980 > URL: https://issues.apache.org/jira/browse/KYLIN-2980 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Trivial > > Pair has no semantic about key/value. And when serializing/deserializing Pair > will both has first/second and key/value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-1664) rest api '/kylin/api/admin/config' without security check
[
https://issues.apache.org/jira/browse/KYLIN-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316104#comment-16316104
]
jiatao.tao commented on KYLIN-1664:
---
Fix a bug and add ut:
https://github.com/apache/kylin/commit/19c4eb79576c102cb1475d7a96ff13db14496712
> rest api '/kylin/api/admin/config' without security check
> -
>
> Key: KYLIN-1664
> URL: https://issues.apache.org/jira/browse/KYLIN-1664
> Project: Kylin
> Issue Type: Bug
> Components: REST Service
>Affects Versions: v1.5.1
> Environment: Ubuntu 14.4
> Jdk 1.7.0
> Kylin 1.5.1 binary
>Reporter: Hanhui LI
>Assignee: Shaofeng SHI
> Labels: test
> Fix For: v2.3.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> rest api '/kylin/api/admin/config' without security check.
> Please check the follwoing:
> ===
> GET Request:
> http://127.0.0.1:7070/kylin/api/admin/config
> Response:
> {"config":"kylin.hbase.region.cut.large=50\nkylin.hbase.default.compression.codec=snappy\ndeploy.env=QA\nacl.adminRole=ROLE_ADMIN\nkylin.sandbox=true\nkylin.hdfs.working.dir=/kylin\nldap.user.searchBase=\nkylin.job.concurrent.max.limit=10\nkylin.job.remote.cli.password=\nsaml.metadata.file=classpath:sso_metadata.xml\nkylin.job.yarn.app.rest.check.interval.seconds=10\nmail.sender=\nmail.password=\nkylin.job.remote.cli.username=\nmail.username=\nsaml.context.serverPort=443\nkylin.web.help.length=4\nkylin.job.run.as.remote.cmd=false\nldap.service.searchPattern=\nkylin.web.contact_mail=\nldap.user.groupSearchBase=\nkylin.hbase.region.cut.small=5\nkylin.web.hive.limit=20\nkylin.job.mapreduce.default.reduce.input.mb=500\nkylin.job.hive.database.for.intermediatetable=default\nkylin.metadata.url=kylin_metadata@hbase\nldap.password=\nldap.username=\nkylin.storage.url=hbase\nganglia.port=8664\nldap.user.searchPattern=\nkylin.job.status.with.kerberos=false\nganglia.group=\nkylin.hbase.cluster.fs=\nacl.defaultRole=ROLE_ANALYST,ROLE_MODELER\nsaml.context.contextPath=/kylin\nmail.host=\nkylin.job.remote.cli.working.dir=/tmp/kylin\nkylin.web.diagnostic=\nsaml.context.scheme=https\nkylin.job.cubing.inmem.sampling.percent=100\nldap.service.groupSearchBase=\nsaml.metadata.entityBaseURL=https://hostname/kylin\nkylin.hbase.hfile.size.gb=5\nldap.service.searchBase=\nkylin.owner=who...@kylin.apache.org\nmail.enabled=false\nkylin.rest.servers=localhost:7070\nkylin.security.profile=testing\nkylin.job.retry=0\nsaml.context.serverName=hostname\nldap.server=ldap://ldap_server:389\nkylin.job.remote.cli.hostname=\nkylin.query.security.enabled=true\nkylin.server.mode=all\nkylin.web.help.3=onboard|Cube
> Design Tutorial|\nkylin.web.help.2=tableau|Tableau
> Guide|\nkylin.web.help.1=odbc|ODBC
> Driver|\nkylin.hbase.region.cut.medium=10\nkylin.web.help.0=start|Getting
> Started|\nkylin.web.hadoop=\nkylin.web.streaming.guide=http://kylin.apache.org/\n"}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (KYLIN-3105) Interface Scheduler's stop method should be removed
[ https://issues.apache.org/jira/browse/KYLIN-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao resolved KYLIN-3105. --- Resolution: Fixed > Interface Scheduler's stop method should be removed > --- > > Key: KYLIN-3105 > URL: https://issues.apache.org/jira/browse/KYLIN-3105 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3105) Interface Scheduler's stop method should be removed
[ https://issues.apache.org/jira/browse/KYLIN-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316101#comment-16316101 ] jiatao.tao commented on KYLIN-3105: --- Here's the commit: https://github.com/apache/kylin/commit/d7ebaec5162d8714ba8c2b86249d4b83cef5fdbe > Interface Scheduler's stop method should be removed > --- > > Key: KYLIN-3105 > URL: https://issues.apache.org/jira/browse/KYLIN-3105 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2960) We should submit a new feature that it support the authentication for user and role and the authentication for user and group when the LDAP authentication was enabled.
[ https://issues.apache.org/jira/browse/KYLIN-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao resolved KYLIN-2960. --- Resolution: Fixed > We should submit a new feature that it support the authentication for user > and role and the authentication for user and group when the LDAP > authentication was enabled. > --- > > Key: KYLIN-2960 > URL: https://issues.apache.org/jira/browse/KYLIN-2960 > Project: Kylin > Issue Type: New Feature > Components: General >Reporter: peng.jianhua >Assignee: jiatao.tao > Labels: patch > Attachments: > 0001-KYLIN-2960-Submit-a-new-feature-that-it-supports-the.patch > > > Currently, the user authentication interface that was provided by kylin to > the third party only supports user and role authentication. However only user > and group have authentication function when we use the LDAP authentication. > In fact the authentication for user and role and the authentication for user > and group have the same functional characteristics between different > appplication system. So we should submit a new feature that it support the > authentication for user and role and the authentication for user and group > when the LDAP authentication was enabled. > We supplied the checkPermission interface to implement the new feature. In > the interface we set user groups information to the userRoles parameter when > the LDAP was enabled, on the contrary we set user roles information to the > userRoles parameter. The interface is as following: > /** > * Checks if a user has permission on an entity. > * > * @param user > * @param userRoles > * @param entityType String constants defined in AclEntityType > * @param entityUuid > * @param permission > * > * @return true if has permission > */ > abstract public boolean checkPermission(String user, List userRoles, > // > String entityType, String entityUuid, Permission permission); -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2960) We should submit a new feature that it support the authentication for user and role and the authentication for user and group when the LDAP authentication was enab
[ https://issues.apache.org/jira/browse/KYLIN-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316097#comment-16316097 ] jiatao.tao edited comment on KYLIN-2960 at 1/8/18 10:53 AM: Here's the commit: https://github.com/apache/kylin/commit/c2f54af6b7e8f8261eb2bb716a0818eaa4dc8c78 was (Author: aron.tao): Here's the commit:https://github.com/apache/kylin/commit/c2f54af6b7e8f8261eb2bb716a0818eaa4dc8c78 > We should submit a new feature that it support the authentication for user > and role and the authentication for user and group when the LDAP > authentication was enabled. > --- > > Key: KYLIN-2960 > URL: https://issues.apache.org/jira/browse/KYLIN-2960 > Project: Kylin > Issue Type: New Feature > Components: General >Reporter: peng.jianhua >Assignee: jiatao.tao > Labels: patch > Attachments: > 0001-KYLIN-2960-Submit-a-new-feature-that-it-supports-the.patch > > > Currently, the user authentication interface that was provided by kylin to > the third party only supports user and role authentication. However only user > and group have authentication function when we use the LDAP authentication. > In fact the authentication for user and role and the authentication for user > and group have the same functional characteristics between different > appplication system. So we should submit a new feature that it support the > authentication for user and role and the authentication for user and group > when the LDAP authentication was enabled. > We supplied the checkPermission interface to implement the new feature. In > the interface we set user groups information to the userRoles parameter when > the LDAP was enabled, on the contrary we set user roles information to the > userRoles parameter. The interface is as following: > /** > * Checks if a user has permission on an entity. > * > * @param user > * @param userRoles > * @param entityType String constants defined in AclEntityType > * @param entityUuid > * @param permission > * > * @return true if has permission > */ > abstract public boolean checkPermission(String user, List userRoles, > // > String entityType, String entityUuid, Permission permission); -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (KYLIN-2960) We should submit a new feature that it support the authentication for user and role and the authentication for user and group when the LDAP authentication w
[ https://issues.apache.org/jira/browse/KYLIN-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao updated KYLIN-2960: -- Comment: was deleted (was: Here's the commit:https://github.com/apache/kylin/commit/c2f54af6b7e8f8261eb2bb716a0818eaa4dc8c78) > We should submit a new feature that it support the authentication for user > and role and the authentication for user and group when the LDAP > authentication was enabled. > --- > > Key: KYLIN-2960 > URL: https://issues.apache.org/jira/browse/KYLIN-2960 > Project: Kylin > Issue Type: New Feature > Components: General >Reporter: peng.jianhua >Assignee: jiatao.tao > Labels: patch > Attachments: > 0001-KYLIN-2960-Submit-a-new-feature-that-it-supports-the.patch > > > Currently, the user authentication interface that was provided by kylin to > the third party only supports user and role authentication. However only user > and group have authentication function when we use the LDAP authentication. > In fact the authentication for user and role and the authentication for user > and group have the same functional characteristics between different > appplication system. So we should submit a new feature that it support the > authentication for user and role and the authentication for user and group > when the LDAP authentication was enabled. > We supplied the checkPermission interface to implement the new feature. In > the interface we set user groups information to the userRoles parameter when > the LDAP was enabled, on the contrary we set user roles information to the > userRoles parameter. The interface is as following: > /** > * Checks if a user has permission on an entity. > * > * @param user > * @param userRoles > * @param entityType String constants defined in AclEntityType > * @param entityUuid > * @param permission > * > * @return true if has permission > */ > abstract public boolean checkPermission(String user, List userRoles, > // > String entityType, String entityUuid, Permission permission); -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2960) We should submit a new feature that it support the authentication for user and role and the authentication for user and group when the LDAP authentication was enabled.
[ https://issues.apache.org/jira/browse/KYLIN-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316095#comment-16316095 ] jiatao.tao commented on KYLIN-2960: --- Here's the commit:https://github.com/apache/kylin/commit/c2f54af6b7e8f8261eb2bb716a0818eaa4dc8c78 > We should submit a new feature that it support the authentication for user > and role and the authentication for user and group when the LDAP > authentication was enabled. > --- > > Key: KYLIN-2960 > URL: https://issues.apache.org/jira/browse/KYLIN-2960 > Project: Kylin > Issue Type: New Feature > Components: General >Reporter: peng.jianhua >Assignee: jiatao.tao > Labels: patch > Attachments: > 0001-KYLIN-2960-Submit-a-new-feature-that-it-supports-the.patch > > > Currently, the user authentication interface that was provided by kylin to > the third party only supports user and role authentication. However only user > and group have authentication function when we use the LDAP authentication. > In fact the authentication for user and role and the authentication for user > and group have the same functional characteristics between different > appplication system. So we should submit a new feature that it support the > authentication for user and role and the authentication for user and group > when the LDAP authentication was enabled. > We supplied the checkPermission interface to implement the new feature. In > the interface we set user groups information to the userRoles parameter when > the LDAP was enabled, on the contrary we set user roles information to the > userRoles parameter. The interface is as following: > /** > * Checks if a user has permission on an entity. > * > * @param user > * @param userRoles > * @param entityType String constants defined in AclEntityType > * @param entityUuid > * @param permission > * > * @return true if has permission > */ > abstract public boolean checkPermission(String user, List userRoles, > // > String entityType, String entityUuid, Permission permission); -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2960) We should submit a new feature that it support the authentication for user and role and the authentication for user and group when the LDAP authentication was enabled.
[ https://issues.apache.org/jira/browse/KYLIN-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316097#comment-16316097 ] jiatao.tao commented on KYLIN-2960: --- Here's the commit:https://github.com/apache/kylin/commit/c2f54af6b7e8f8261eb2bb716a0818eaa4dc8c78 > We should submit a new feature that it support the authentication for user > and role and the authentication for user and group when the LDAP > authentication was enabled. > --- > > Key: KYLIN-2960 > URL: https://issues.apache.org/jira/browse/KYLIN-2960 > Project: Kylin > Issue Type: New Feature > Components: General >Reporter: peng.jianhua >Assignee: jiatao.tao > Labels: patch > Attachments: > 0001-KYLIN-2960-Submit-a-new-feature-that-it-supports-the.patch > > > Currently, the user authentication interface that was provided by kylin to > the third party only supports user and role authentication. However only user > and group have authentication function when we use the LDAP authentication. > In fact the authentication for user and role and the authentication for user > and group have the same functional characteristics between different > appplication system. So we should submit a new feature that it support the > authentication for user and role and the authentication for user and group > when the LDAP authentication was enabled. > We supplied the checkPermission interface to implement the new feature. In > the interface we set user groups information to the userRoles parameter when > the LDAP was enabled, on the contrary we set user roles information to the > userRoles parameter. The interface is as following: > /** > * Checks if a user has permission on an entity. > * > * @param user > * @param userRoles > * @param entityType String constants defined in AclEntityType > * @param entityUuid > * @param permission > * > * @return true if has permission > */ > abstract public boolean checkPermission(String user, List userRoles, > // > String entityType, String entityUuid, Permission permission); -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (KYLIN-2960) We should submit a new feature that it support the authentication for user and role and the authentication for user and group when the LDAP authentication w
[ https://issues.apache.org/jira/browse/KYLIN-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao updated KYLIN-2960: -- Comment: was deleted (was: Here's the commit:https://github.com/apache/kylin/commit/c2f54af6b7e8f8261eb2bb716a0818eaa4dc8c78) > We should submit a new feature that it support the authentication for user > and role and the authentication for user and group when the LDAP > authentication was enabled. > --- > > Key: KYLIN-2960 > URL: https://issues.apache.org/jira/browse/KYLIN-2960 > Project: Kylin > Issue Type: New Feature > Components: General >Reporter: peng.jianhua >Assignee: jiatao.tao > Labels: patch > Attachments: > 0001-KYLIN-2960-Submit-a-new-feature-that-it-supports-the.patch > > > Currently, the user authentication interface that was provided by kylin to > the third party only supports user and role authentication. However only user > and group have authentication function when we use the LDAP authentication. > In fact the authentication for user and role and the authentication for user > and group have the same functional characteristics between different > appplication system. So we should submit a new feature that it support the > authentication for user and role and the authentication for user and group > when the LDAP authentication was enabled. > We supplied the checkPermission interface to implement the new feature. In > the interface we set user groups information to the userRoles parameter when > the LDAP was enabled, on the contrary we set user roles information to the > userRoles parameter. The interface is as following: > /** > * Checks if a user has permission on an entity. > * > * @param user > * @param userRoles > * @param entityType String constants defined in AclEntityType > * @param entityUuid > * @param permission > * > * @return true if has permission > */ > abstract public boolean checkPermission(String user, List userRoles, > // > String entityType, String entityUuid, Permission permission); -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2960) We should submit a new feature that it support the authentication for user and role and the authentication for user and group when the LDAP authentication was enabled.
[ https://issues.apache.org/jira/browse/KYLIN-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316094#comment-16316094 ] jiatao.tao commented on KYLIN-2960: --- Here's the commit:https://github.com/apache/kylin/commit/c2f54af6b7e8f8261eb2bb716a0818eaa4dc8c78 > We should submit a new feature that it support the authentication for user > and role and the authentication for user and group when the LDAP > authentication was enabled. > --- > > Key: KYLIN-2960 > URL: https://issues.apache.org/jira/browse/KYLIN-2960 > Project: Kylin > Issue Type: New Feature > Components: General >Reporter: peng.jianhua >Assignee: jiatao.tao > Labels: patch > Attachments: > 0001-KYLIN-2960-Submit-a-new-feature-that-it-supports-the.patch > > > Currently, the user authentication interface that was provided by kylin to > the third party only supports user and role authentication. However only user > and group have authentication function when we use the LDAP authentication. > In fact the authentication for user and role and the authentication for user > and group have the same functional characteristics between different > appplication system. So we should submit a new feature that it support the > authentication for user and role and the authentication for user and group > when the LDAP authentication was enabled. > We supplied the checkPermission interface to implement the new feature. In > the interface we set user groups information to the userRoles parameter when > the LDAP was enabled, on the contrary we set user roles information to the > userRoles parameter. The interface is as following: > /** > * Checks if a user has permission on an entity. > * > * @param user > * @param userRoles > * @param entityType String constants defined in AclEntityType > * @param entityUuid > * @param permission > * > * @return true if has permission > */ > abstract public boolean checkPermission(String user, List userRoles, > // > String entityType, String entityUuid, Permission permission); -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (KYLIN-3108) Change IT embedded Kafka broker path to /kylin/streaming_config/UUID
[ https://issues.apache.org/jira/browse/KYLIN-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao updated KYLIN-3108: -- Comment: was deleted (was: https://github.com/apache/kylin/commit/9c8565465a7bc2d9b227900e3a6cf841e919d49e) > Change IT embedded Kafka broker path to /kylin/streaming_config/UUID > > > Key: KYLIN-3108 > URL: https://issues.apache.org/jira/browse/KYLIN-3108 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > > In IT BuildCubeWithStream, will connect to zk with chroot path: "/" + > UUID.randomUUID(), should move this to /kylin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-3108) Change IT embedded Kafka broker path to /kylin/streaming_config/UUID
[ https://issues.apache.org/jira/browse/KYLIN-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316086#comment-16316086 ] jiatao.tao edited comment on KYLIN-3108 at 1/8/18 10:50 AM: here's the commit: https://github.com/apache/kylin/commit/9c8565465a7bc2d9b227900e3a6cf841e919d49e was (Author: aron.tao): https://github.com/apache/kylin/commit/9c8565465a7bc2d9b227900e3a6cf841e919d49e > Change IT embedded Kafka broker path to /kylin/streaming_config/UUID > > > Key: KYLIN-3108 > URL: https://issues.apache.org/jira/browse/KYLIN-3108 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > > In IT BuildCubeWithStream, will connect to zk with chroot path: "/" + > UUID.randomUUID(), should move this to /kylin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3108) Change IT embedded Kafka broker path to /kylin/streaming_config/UUID
[ https://issues.apache.org/jira/browse/KYLIN-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316085#comment-16316085 ] jiatao.tao commented on KYLIN-3108: --- https://github.com/apache/kylin/commit/9c8565465a7bc2d9b227900e3a6cf841e919d49e > Change IT embedded Kafka broker path to /kylin/streaming_config/UUID > > > Key: KYLIN-3108 > URL: https://issues.apache.org/jira/browse/KYLIN-3108 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > > In IT BuildCubeWithStream, will connect to zk with chroot path: "/" + > UUID.randomUUID(), should move this to /kylin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-3108) Change IT embedded Kafka broker path to /kylin/streaming_config/UUID
[ https://issues.apache.org/jira/browse/KYLIN-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao resolved KYLIN-3108. --- Resolution: Fixed https://github.com/apache/kylin/commit/9c8565465a7bc2d9b227900e3a6cf841e919d49e > Change IT embedded Kafka broker path to /kylin/streaming_config/UUID > > > Key: KYLIN-3108 > URL: https://issues.apache.org/jira/browse/KYLIN-3108 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > > In IT BuildCubeWithStream, will connect to zk with chroot path: "/" + > UUID.randomUUID(), should move this to /kylin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (KYLIN-3108) Change IT embedded Kafka broker path to /kylin/streaming_config/UUID
[ https://issues.apache.org/jira/browse/KYLIN-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao updated KYLIN-3108: -- Comment: was deleted (was: https://github.com/apache/kylin/commit/9c8565465a7bc2d9b227900e3a6cf841e919d49e) > Change IT embedded Kafka broker path to /kylin/streaming_config/UUID > > > Key: KYLIN-3108 > URL: https://issues.apache.org/jira/browse/KYLIN-3108 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > > In IT BuildCubeWithStream, will connect to zk with chroot path: "/" + > UUID.randomUUID(), should move this to /kylin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2760) Enhance Project Level ACL
[ https://issues.apache.org/jira/browse/KYLIN-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao resolved KYLIN-2760. --- Resolution: Fixed > Enhance Project Level ACL > - > > Key: KYLIN-2760 > URL: https://issues.apache.org/jira/browse/KYLIN-2760 > Project: Kylin > Issue Type: Improvement > Components: General >Affects Versions: v2.0.0 > Environment: all >Reporter: Joanna He >Assignee: jiatao.tao > Attachments: screenshot-1.png > > > We are planning on enhancing the project level ACL, the plan as below: > There are five types of predefined user access: System Admin, Project Admin, > Management, Operation and Query. > When syncing an LDAP new user, admin has the option to set the new user as > system admin. The other user access, however, need to be set at project > level, that means other than system admin which is applied globally on an > instance, the other four user access are granted on project by project basis. > So that one user, say johndoe, can be project admin in Project A and > management access in Project B. > User role modeler and analyst that are currently set when syncing users, will > be retired. Project level access can be assigned to user, but not on role any > more. > Cube level ACL will be retired too, user's access control on a cube will be > inherited from user's project level ACL. > The expected access level for those 5 types of user access are defined as > attached. > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2760) Enhance Project Level ACL
[ https://issues.apache.org/jira/browse/KYLIN-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316045#comment-16316045 ] jiatao.tao commented on KYLIN-2760: --- here's the commit:https://github.com/apache/kylin/commit/7a9f74c8a0f70480f40c6e88e0aeb71824fd7884 > Enhance Project Level ACL > - > > Key: KYLIN-2760 > URL: https://issues.apache.org/jira/browse/KYLIN-2760 > Project: Kylin > Issue Type: Improvement > Components: General >Affects Versions: v2.0.0 > Environment: all >Reporter: Joanna He >Assignee: jiatao.tao > Attachments: screenshot-1.png > > > We are planning on enhancing the project level ACL, the plan as below: > There are five types of predefined user access: System Admin, Project Admin, > Management, Operation and Query. > When syncing an LDAP new user, admin has the option to set the new user as > system admin. The other user access, however, need to be set at project > level, that means other than system admin which is applied globally on an > instance, the other four user access are granted on project by project basis. > So that one user, say johndoe, can be project admin in Project A and > management access in Project B. > User role modeler and analyst that are currently set when syncing users, will > be retired. Project level access can be assigned to user, but not on role any > more. > Cube level ACL will be retired too, user's access control on a cube will be > inherited from user's project level ACL. > The expected access level for those 5 types of user access are defined as > attached. > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-3157) Kylin' s timeout has some problems and need to be improvement
jiatao.tao created KYLIN-3157: - Summary: Kylin' s timeout has some problems and need to be improvement Key: KYLIN-3157 URL: https://issues.apache.org/jira/browse/KYLIN-3157 Project: Kylin Issue Type: Improvement Reporter: jiatao.tao Assignee: jiatao.tao Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3157) Enhance Kylin' s timeout
[ https://issues.apache.org/jira/browse/KYLIN-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao updated KYLIN-3157: -- Description: Nowadays, kylin's query timeout( kylin.query.timeout-seconds ) is only for one OLAP context, should be for the entire query life cycle. (was: Nowadays, kylin's query timeout(kylin.query.timeout-seconds) has some problems: 1. timeout is only for one OLAP context 2. 3. ) > Enhance Kylin' s timeout > > > Key: KYLIN-3157 > URL: https://issues.apache.org/jira/browse/KYLIN-3157 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > > Nowadays, kylin's query timeout( kylin.query.timeout-seconds ) is only for > one OLAP context, should be for the entire query life cycle. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3157) Enhance Kylin' s timeout
[ https://issues.apache.org/jira/browse/KYLIN-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao updated KYLIN-3157: -- Summary: Enhance Kylin' s timeout (was: Kylin' s timeout has some problems and need to be improvement ) > Enhance Kylin' s timeout > > > Key: KYLIN-3157 > URL: https://issues.apache.org/jira/browse/KYLIN-3157 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > > Nowadays, kylin's query timeout(kylin.query.timeout-seconds) has some > problems: > 1. timeout is only for one OLAP context > 2. > 3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3157) Kylin' s timeout has some problems and need to be improvement
[ https://issues.apache.org/jira/browse/KYLIN-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao updated KYLIN-3157: -- Description: Nowadays, kylin's query timeout(kylin.query.timeout-seconds) has some problems: 1. timeout is only for one OLAP context 2. 3. > Kylin' s timeout has some problems and need to be improvement > -- > > Key: KYLIN-3157 > URL: https://issues.apache.org/jira/browse/KYLIN-3157 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > > Nowadays, kylin's query timeout(kylin.query.timeout-seconds) has some > problems: > 1. timeout is only for one OLAP context > 2. > 3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
