[
https://issues.apache.org/jira/browse/METAMODEL-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744791#comment-13744791
]
Kasper Sørensen commented on METAMODEL-21:
------------------------------------------
Sounds like a good idea. I think the best option would even be to simply make a
SQL dialect in the existing JDBC module for the Phoenix driver. As long as it's
more or less just a matter of using UPSERT instead of INSERT or UPDATE, I think
a dialect will do fine (if not, we should improve the dialect interface so it
is possible).
> 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
> Assignee: Henry Saputra
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
