[jira] [Updated] (KYLIN-2668) Support Calcites Properties in JDBC URL

["Billy Liu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KYLIN-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Billy Liu updated KYLIN-2668:
-----------------------------
    Issue Type: Improvement  (was: Bug)
       Summary: Support Calcites Properties in JDBC URL  (was: Kylin JDBC Driver doesn't support Calcites Properties in URL)

> Support Calcites Properties in JDBC URL
> ---------------------------------------
>
>                 Key: KYLIN-2668
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2668
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Driver - JDBC
>    Affects Versions: 1.x-HBase1.1.3
>            Reporter: Joe Swingle
>            Assignee: Joe Swingle
>             Fix For: v2.1.0
>
>         Attachments: KYLIN-2668-v2.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)