[Report] Apache Kylin - May 2020
Hello, forks, below the board report of Kylin. ## Description: The mission of Apache Kylin is the creation and maintenance of software related to a distributed and scalable OLAP engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Kylin was founded 2015-11-18 (4 years ago) There are currently 40 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Chunen Ni on 2019-11-26. - Kaige Liu was added as a committer on 2020-03-24 ## Project Activity: Released two bug-fix releases in the first quarter of 2020. The v2.6.6, v3.0.2, and v3.1.0 are also on the way. And several contributors are working on the parquet storage which is planned in Kylin v4.0. The community holds several online meetups: - March 14, Kylin + Hudi online meetup, Shaofeng Li, Tianpeng Zhou and Shaofeng Shi shared Hudi, Kylin realtime, and "Hudi + Kylin for NRT data warehouse" topics; - April 9, Kylin on Parquet quick start the online webinar, Rupeng Wang, Yiming Xu shared Kylin on Parquet technologies and performance data. - April 9, Apache Kylin 101: Get Sub-Second Analytics on Massive Datasets, Kaige Liu introduced the basic concepts of Kylin in the online webinar Recent releases: 2.6.5 was released on 2020-02-19. 3.0.1 was released on 2020-02-19. 3.0.0 was released on 2019-12-18. ## Community Health: Due to the Chinese Spring festival and the impact of COVID-19, the activity in the past quarter is less than last year. dev@kylin.apache.org had a 16% decrease in traffic in the past quarter (251 emails compared to 297) u...@kylin.apache.org had a 55% decrease in traffic in the past quarter (102 emails compared to 226) 105 issues opened in JIRA, past quarter (-21% decrease) 133 issues closed in JIRA, past quarter (34% increase) 153 commits in the past quarter (-54% decrease) 45 code contributors in the past quarter (-6% decrease) 89 PRs opened on GitHub, past quarter (-50% decrease) 86 PRs closed on GitHub, past quarter (-54% decrease) Best regards, Shaofeng Shi 史少锋 Apache Kylin PMC Email: shaofeng...@apache.org Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html Join Kylin user mail group: user-subscr...@kylin.apache.org Join Kylin dev mail group: dev-subscr...@kylin.apache.org
[jira] [Created] (KYLIN-4481) Project-level ACL lookups not working for non-admin SAML-federated users
Rafael Felix Correa created KYLIN-4481:
--
Summary: Project-level ACL lookups not working for non-admin
SAML-federated users
Key: KYLIN-4481
URL: https://issues.apache.org/jira/browse/KYLIN-4481
Project: Kylin
Issue Type: Bug
Components: Security
Affects Versions: v3.0.1, v2.6.5
Reporter: Rafael Felix Correa
Steps to reproduce:
* setup kylin with SAML as described in
[http://kylin.apache.org/docs/howto/howto_ldap_and_sso.html]. kylin.properties:
{code:java}
kylin.security.profile=saml
kylin.security.acl.admin-role=Kylin_Admins
kylin.security.ldap.connection-server=ldap://openldap:389
kylin.security.ldap.connection-username=cn=admin,dc=example,dc=org
# set kylin.security.ldap.connection-password appropriately
kylin.security.ldap.user-search-base=ou=people,dc=example,dc=org
kylin.security.ldap.user-search-pattern=(uid={0})
kylin.security.ldap.user-group-search-base=ou=groups,dc=example,dc=org
kylin.security.saml.context-context-path=/kylin
kylin.security.saml.context-scheme=https
kylin.security.saml.context-server-name=kylin.validdomain.com
kylin.security.saml.context-server-port=443
kylin.security.saml.metadata-entity-base-url=https://kylin.validdomain.com/kylin{code}
* on the LDAP server, make sure you have the following objects in place:
{code:java}
# example.user, people, example.org
dn: uid=example.user,ou=people,dc=example,dc=org
objectClass: top
objectClass: account
objectClass: posixAccount
objectClass: shadowAccount
gidNumber: 1
uidNumber: 5000
cn: Does not matter
homeDirectory: /home/doesntmatter
uid: example.user{code}
*
{code:java}
# Kylin_Users, groups, example.org
dn: cn=Kylin_Users,ou=groups,dc=example,dc=org
objectClass: top
objectClass: groupOfNames
cn: Kylin_Users
member: uid=example.user,ou=people,dc=example,dc=org{code}
* as an ADMIN, create a sample project in kylin and grant QUERY, MANAGEMENT or
OPERATION access to example.user.
* now, try logging into kylin.validdomain.com's Web UI as
[example.u...@validdomain.com.|mailto:example.u...@validdomain.com.]
Expected result:
* example.user is logged in, able to select the project from the dropdown box
at the top left corner and navigate through its properties.
Actual result:
* example.user is logged in, but no projects are listed in the dropdown box.
As if he/she had no permissions in any project.
With LDAP-pure installations (no SAML), this configuration works as expected.
Worth noting:
[https://github.com/apache/kylin/blob/kylin-3.0.1/server-base/src/main/java/org/apache/kylin/rest/security/SAMLUserDetailsService.java#L40-L54]
splits the user in the '@' char for performing LDAP lookups. However, by
editing kylin_metadata manually and appending the @validdomain.com to the
corresponding object under /acls, the lookup works as it should and the
non-admin user gets to access the sample project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (KYLIN-4480) Implement runtime non-equi join
Li Xian created KYLIN-4480:
--
Summary: Implement runtime non-equi join
Key: KYLIN-4480
URL: https://issues.apache.org/jira/browse/KYLIN-4480
Project: Kylin
Issue Type: New Feature
Components: Query Engine
Reporter: Li Xian
Currently Kylin does not support non-equi join. This issue is aim to add
runtime non-equi join feature to Kylin so that queries like
{code:java}
select
|
non-equi join
/\
subquery1 subquery2
{code}
can now be executed like below. Kylin will read data from subquery cubes and do
non-equi join during runtime
{code:java}
select
|
runtime non-equi join
/\
cube1 cube2
{code}
I have submitted a PR for this issue
[https://github.com/apache/kylin/pull/1195]
[https://github.com/Kyligence/calcite/pull/133]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
