Kylin Connector

The Kylin connector allows querying tables in an external Kylin database. This can be used to join data between different systems like Kylin and Hive, or between two different Kylin instances.

Configuration

To configure the Kylin connector, create a catalog properties file inetc/catalog named, for example, Kylin.properties, to mount the Kylin connector as the Kylin catalog. Create the file with the following contents, replacing the connection properties as appropriate for your setup:

connector.name=kylin
connection-url=jdbc:kylin://example.net/project
connection-user=root
connection-password=secret
connector-planoptimizer-rule-blacklist=io.prestosql.sql.planner.iterative.rule.SingleDistinctAggregationToGroupBy

The connector-planoptimizer-rule-blacklist attribute is specially configured for kylin, and the default value is io.prestosql.sql.planner.iterative.rule.SingleDistinctAggregationToGroupBy

Multiple Kylin Servers

You can have as many catalogs as you need, so if you have additional Kylin servers, simply add another properties file to etc/catalog with a different name (making sure it ends in .properties). For example, if you name the property file sales.properties, openLooKeng will create a catalog named sales using the configured connector.

Querying Kylin

you can access the clicks table in the web database:

SELECT * FROM Kylin.web.clicks;

If you used a different name for your catalog properties file, use that catalog name instead of Kylin in the above examples.

Kylin Connector Limitations

The following SQL statements are not yet supported:

DELETE、../sql/update.md)、../sql/delete.html)、GRANTREVOKESHOW GRANTSSHOW ROLESSHOW ROLE GRANTS

有奖捉虫

“有虫”文档片段

0/500

存在的问题

文档存在风险与错误

● 拼写,格式,无效链接等错误;

● 技术原理、功能、规格等描述和软件不一致,存在错误;

● 原理图、架构图等存在错误;

● 版本号不匹配:文档版本或内容描述和实际软件不一致;

● 对重要数据或系统存在风险的操作,缺少安全提示;

● 排版不美观,影响阅读;

内容描述不清晰

● 描述存在歧义;

● 图形、表格、文字等晦涩难懂;

● 逻辑不清晰,该分类、分项、分步骤的没有给出;

内容获取有困难

● 很难通过搜索引擎,openLooKeng官网,相关博客找到所需内容;

示例代码有错误

● 命令、命令参数等错误;

● 命令无法执行或无法完成对应功能;

内容有缺失

● 关键步骤错误或缺失,无法指导用户完成任务,比如安装、配置、部署等;

● 逻辑不清晰,该分类、分项、分步骤的没有给出

● 图形、表格、文字等晦涩难懂

● 缺少必要的前提条件、注意事项等;

● 描述存在歧义

0/500

您对文档的总体满意度

非常不满意
非常满意

请问是什么原因让您参与到这个问题中

您的邮箱

创Issue赢奖品
根据您的反馈,会自动生成issue模板。您只需点击按钮,创建issue即可。
有奖捉虫