Database Reference
In-Depth Information
row user=178 : not found
query time : 0.004097 ms
querying for userId : 83
email=user-83@foo.com
query time : 0.003783 ms
querying for userId : 7
email=user-7@foo.com
query time : 0.003616 ms
querying for userId : 129
row user=129 : not found
query time : 0.003506 ms
However, this is all just done to check your ammo. In order to have a clear picture
of the HBase design patterns, we should describe it in a clear, unambiguous, precise
language, and what language would be better for querying databases than SQL.
A question might arise that HBase is a NoSQL database. This means that it does
not understand SQL. Well, that was a while back. Nowadays, NoSQL means Not
Only SQL .
Project Phoenix — a SQL for HBase
Phoenix is a relatively recent project that represents a SQL layer over HBase. Its blog
is at http://phoenix-hbase.blogspot.com/ , and it was first announced at this
blog on January 30, 2013.
Here is a brief list of only some of the capabilities that it gives you:
• Phoenix allows columns to be modeled as a multi-part row key or
key/value cells
• It provides full query support with predicate pushdown and optimal
scan key formation
• It provides DDL support ( CREATE TABLE , DROP TABLE , and ALTER TABLE)
to add/remove columns
• It provides DML support, UPSERT VALUES for row-by-row insertion, UPSERT
SELECT for mass data transfer between the same or different tables, and
DELETE for deleting rows
 
Search WWH ::




Custom Search