[
https://issues.jboss.org/browse/TEIID-2816?page=com.atlassian.jira.plugin...
]
Kylin Soong commented on TEIID-2816:
------------------------------------
that this solution is phoenix specific, such as the translator name?
I changed my mind today, I think we do not need change the translator name, hbase is
more suitabe name, cause we get data from hbase, phoenix just like a Hbase driver.
We may need document install phoenix server jar to HBase RegionServer lib folder, execute
phoenix DDL to create/map table are precondition for running hbase translator.
In addition, I have updated the unit test, correct some init DDL, and made
'Customer' table as a example for showing how hbase translator work with lower
words column families table in HBase. The unit test can run fine now.
HBase Connector/Translator
--------------------------
Key: TEIID-2816
URL:
https://issues.jboss.org/browse/TEIID-2816
Project: Teiid
Issue Type: Feature Request
Components: Connector API, JDBC Connector, JDBC Driver
Affects Versions: Open To Community
Reporter: devin pinkston
Assignee: Kylin Soong
Labels: HBase, Translator
Fix For: 8.10
Develop a HBase translator/connector. Potentially using the Phoenix JDBC driver,
supports most SQL and handles connections:
https://github.com/forcedotcom/phoenix
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)