[ 
https://issues.apache.org/jira/browse/LIVY-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578226#comment-16578226
 ] 

Marco Gaido commented on LIVY-489:
----------------------------------

Sure [~jerryshao], the branch is 
https://github.com/mgaido91/incubator-livy/tree/livy_thrift, and the diff is 
https://github.com/apache/incubator-livy/compare/master...mgaido91:livy_thrift.

> Expose a JDBC endpoint for Livy
> -------------------------------
>
>                 Key: LIVY-489
>                 URL: https://issues.apache.org/jira/browse/LIVY-489
>             Project: Livy
>          Issue Type: New Feature
>          Components: API, Server
>    Affects Versions: 0.6.0
>            Reporter: Marco Gaido
>            Priority: Major
>
> Many users and BI tools use JDBC connections in order to retrieve data. As 
> Livy exposes only a REST API, this is a limitation in its adoption. Hence, 
> adding a JDBC endpoint may be a very useful feature, which could also make 
> Livy a more attractive solution for end user to adopt.
> Moreover, currently, Spark exposes a JDBC interface, but this has many 
> limitations, including that all the queries are submitted to the same 
> application, therefore there is no isolation/security, which can be offered 
> by Livy, making a Livy JDBC API a better solution for companies/users who 
> want to use Spark in order to run they queries through JDBC.
> In order to make the transition from existing solutions to the new JDBC 
> server seamless, the proposal is to use the Hive thrift-server and extend it 
> as it was done by the STS.
> [Here, you can find the design 
> doc.|https://docs.google.com/document/d/18HAR_VnQLegbYyzGg8f4zwD4GtDP5q_t3K21eXecZC4/edit]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to