kyligence/insight-for-superset

Kyligence Insight for Superset

insight-for-superset's Issues

can't login

I write
username:admin
password:admin

But Invalid login. Please try again.

京东云MarketPlace

Expected results

1.总目标：对接京东云JMR指导并完成KC测试；
2.提供集群部署文档并指导京东云完成安装及解答相关问题;
3.提供安装手册文档，包括：a.文档中说计算、存储资源的标，如建议虚机的配置；b.指导京东云安装；

使用docker镜像编辑数据库

Kyligence Insight for Superset version

docker 镜像最新版的

kylinpy version

Expected results

编辑数据库-->测试连接功能 希望能够测试数据库是否能够正常连接上

Actual results

结果爆出异常
ERROR: {"error": "Connection failed!\n\nThe error message returned was:\n/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18: version `libmysqlclient_18' not found (required by /usr/local/lib/python3.6/site-packages/_mysql.cpython-36m-x86_64-linux-gnu.so)"}

Steps to reproduce

官网注册不了

Kyligence Account 账户注册没反应，报错了

mysql数据源连接失败

ERROR: {"error": "Connection failed!\n\nThe error message returned was:\n/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18: version `libmysqlclient_18' not found (required by /usr/local/lib/python3.6/site-packages/_mysql.cpython-36m-x86_64-linux-gnu.so)"}

Kyligence cloud上cube同步问题

从Kyligence Cloud上登录Superset后，点击Refresh Kylin Cube，然后登出Superset再登录时，看不到之前同步的Cube，需要再重新同步

The file exported by superset in CSV format appears Chinese gibberish

superset report show

export CSV file

The exported CSV format is as follows:

solution

This problem is caused by the language format supported by Superset itself, and the exported format needs to be configured in superset_config.py:

CSV_EXPORT = {
    'encoding' : 'utf_8_sig',
}

test result

Modify the configuration file, start the container, and download the CSV file, which is as follows:

refresh kylin cubes failed

Kyligence Insight for Superset version

The latest docker images for Insight-for-Superset project:
kyligence/superset-kylin:latest

Expected results

After the refresh operation, the cube information should be listed

Actual results

Not output, leaving a blank.

The analysis process

When I refresh Cube, check the kylin log as follows:
2018-07-19 18:11:11,223 DEBUG [http-bio-7070-exec-5] security.KylinAclPermissionEvaluator:97 : Checking permission 'READ' for object 'org.springframework.security.acls.domain.ObjectIdentityImpl[Type: org.apache.kylin.metadata.project.ProjectInstance; Identifier: 2fbca32a-a33e-4b69-83dd-0bb8b1f8c91b]'
2018-07-19 18:11:11,223 DEBUG [http-bio-7070-exec-5] security.KylinAclPermissionEvaluator:120 : Returning false - no ACLs apply for this principal
2018-07-19 18:11:11,223 DEBUG [http-bio-7070-exec-5] security.KylinAclPermissionEvaluator:97 : Checking permission 'ADMINISTRATION' for object 'org.springframework.security.acls.domain.ObjectIdentityImpl[Type: org.apache.kylin.metadata.project.ProjectInstance; Identifier: 2eaca32a-a33e-4b69-83dd-0bb8b1f8c91b]'
2018-07-19 18:11:11,223 DEBUG [http-bio-7070-exec-5] security.KylinAclPermissionEvaluator:120 : Returning false - no ACLs apply for this principal
2018-07-19 18:11:11,224 DEBUG [http-bio-7070-exec-5] security.KylinAclPermissionEvaluator:97 : Checking permission 'MANAGEMENT' for object 'org.springframework.security.acls.domain.ObjectIdentityImpl[Type: org.apache.kylin.metadata.project.ProjectInstance; Identifier: 2eaca32a-a33e-4b69-83dd-0bb8b1f8c91b]'
2018-07-19 18:11:11,224 DEBUG [http-bio-7070-exec-5] security.KylinAclPermissionEvaluator:120 : Returning false - no ACLs apply for this principal
2018-07-19 18:11:11,224 DEBUG [http-bio-7070-exec-5] security.KylinAclPermissionEvaluator:97 : Checking permission 'OPERATION' for object 'org.springframework.security.acls.domain.ObjectIdentityImpl[Type: org.apache.kylin.metadata.project.ProjectInstance; Identifier: 2eaca32a-a33e-4b69-83dd-0bb8b1f8c91b]'
2018-07-19 18:11:11,224 DEBUG [http-bio-7070-exec-5] security.KylinAclPermissionEvaluator:120 : Returning false - no ACLs apply for this principal
2018-07-19 18:11:11,225 DEBUG [http-bio-7070-exec-5] security.KylinAclPermissionEvaluator:97 : Checking permission 'READ' for object 'org.springframework.security.acls.domain.ObjectIdentityImpl[Type: org.apache.kylin.metadata.project.ProjectInstance; Identifier: 2eaca32a-a33e-4b69-83dd-0bb8b1f8c91b]'
2018-07-19 18:11:11,225 DEBUG [http-bio-7070-exec-5] security.KylinAclPermissionEvaluator:120 : Returning false - no ACLs apply for this principal

So, I guess it's related to permissions. I found a parameter in the kylin_auth.py file:
KYLIN_ADMIN_ROLE='ROLE_ADMIN'

Because my kylin environment integrates OpenLDAP, related parameters as follows:
kylin.security.profile=ldap
kylin.security.acl.admin-role=kylin_group

So I modify the value 'ROLE_ADMIN' to the new value "kylin_group", the same error occurred.
Superset itself is normal to query kylin, but just this 'Refresh Kylin Cubes' feature is not available.

Please help, thanks.