You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metamodel.apache.org by "Kasper Sørensen (JIRA)" <ji...@apache.org> on 2014/04/06 11:44:14 UTC

[jira] [Commented] (METAMODEL-21) Add HBase/Phoenix support for MetaModel

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

Kasper Sørensen commented on METAMODEL-21:
------------------------------------------

Ian, I was wondering if you could try to run some simple tests using MetaModel JDBC module towards the Phoenix JDBC driver? Is the JDBC metadata API of the Phoenix driver fully supported, or do we need to apply other tricks to use Phoenix properly?

> Add HBase/Phoenix support for MetaModel
> ---------------------------------------
>
>                 Key: METAMODEL-21
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-21
>             Project: Metamodel
>          Issue Type: New Feature
>            Reporter: Ian Varley
>
> In METAMODEL-13, HBase support is proposed using the HBase java client API directly. This is a good thing to build. In addition, though, it'd be interesting to also try out building a module on top of Phoenix (a "SQL skin" on HBase that uses the java client API directly to transform SQL queries into an optimized run plan, including server-side optimizations using coprocessors). This should be independent of the direct HBase module (which doesn't require use of Phoenix on the HBase cluster), but would be a compelling addition. It's also possible this could be done just with the existing JDBC mm module, but there are some differences from standard SQL (like the use of UPSERT instead of INSERT and UPDATE) that might require a specialized module (perhaps a subclass of the jdbc version). 



--
This message was sent by Atlassian JIRA
(v6.2#6252)