You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/01/24 05:01:39 UTC

[jira] [Resolved] (PHOENIX-676) Implement thin JDBC driver

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

James Taylor resolved PHOENIX-676.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 4.3.0

Fixed by [~ndimiduk] and [~elserj].

> Implement thin JDBC driver
> --------------------------
>
>                 Key: PHOENIX-676
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-676
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: James Taylor
>             Fix For: 4.3.0
>
>
> Currently, the Phoenix JDBC driver is a rather fat, embedded driver, as it needs to include all of the HBase client dependencies to enable the driver to communicate with the HBase server(s). Although this works fine when the application is a web application that already includes the HBase jars on the classpath, it's less than idea in other circumstances.
> We should look at the framework [Optiq](https://github.com/julianhyde/optiq) has for creating a thin driver. @julianhyde can likely elaborate on what would be necessary. We'd need to then have a standalone Phoenix server, perhaps co-resident with one of the server machines in the cluster?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)