[
https://issues.apache.org/jira/browse/KYLIN-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064838#comment-16064838
]
Billy Liu commented on KYLIN-2668:
----------------------------------
Thanks [~joe.swingle], code LGTM, but the patch subject seems unreadable, which
is "Subject: [PATCH] =?UTF-8?q?Fix=20for=20KYLIN-2668.=20=20Added=20Regex=20to?=
=?UTF-8?q?=20accept=20after=20=E2=80=98jdbc:kylin:=E2=80=99=20=20up=20to?=
=?UTF-8?q?=20the=20=E2=80=98//=E2=80=98.=20=20and=20parsed=20out=20as=20p?=
=?UTF-8?q?roperties.?="
> Kylin JDBC Driver doesn't support Calcites Properties in URL
> ------------------------------------------------------------
>
> Key: KYLIN-2668
> URL: https://issues.apache.org/jira/browse/KYLIN-2668
> Project: Kylin
> Issue Type: Bug
> Components: Driver - JDBC
> Affects Versions: 1.x-HBase1.1.3
> Reporter: Joe Swingle
> Attachments: KYLIN-2668.patch
>
>
> We currently access our OLAP Cubes in Kylin from our BI Tool over JDBC. We
> run Kylin over SSL. When using our COTS BI Tool, we cannot programmatically
> pass in property values such as ssl=True into a java.util.Properties. We
> can only specify a Username, Password and URL.
> According to Calcite we should be able to provide some properties in the JDBC
> URL. Line 142 of org.apache.calcite.avatica.UnregisteredDriver, builds java
> properties based on the URL. This works for Kylin. For example,
> "jdbc:kylin:ssl=True;//kylinserver.com/Projectname" Will correctly
> establish the connection as using SSL.
> The problem is in KylinConnection's Constructor. It splits the jdbcURL on
> "jdbc:kylin://". So, it ignores the SSL. (KylinConnection. Line 54-60.)
> The KylinConnection needs to be updated to support this method for setting
> properties, so it can be used by 3rd party applications where programing the
> connection is not possible.
> We have coded this locally, and will submit patch.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
