hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-hadoop Wiki] Update of "Hbase/HbaseArchitecture" by JimKellerman
Date Mon, 05 Feb 2007 20:16:59 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-hadoop Wiki" for change notification.

The following page has been changed by JimKellerman:
http://wiki.apache.org/lucene-hadoop/Hbase/HbaseArchitecture

The comment on the change is:
Move architectural comments to this page.

------------------------------------------------------------------------------
   * Map/Reduce connector
   * Client Sawzall script execution in Tablet server space
  
+ = Comments =
+ 
+ Please add comments about the architecture below. In the future, as this page grows too
big, it will be split into multiple sub-pages based on the architectural component. Applicable
comments will then be moved to that page. At that point, comments on this page should be related
to an overall architectural issue or one that spans multiple components. Thank you.
+ 
+ ----
+ 
+ === It is not Row-Oriented. ===
+ 
+ by [wiki:udanax Udanax] [[MailTo(webmaster AT SPAMFREE udanax DOT org)]]
+ 
+ It's need to be much smaller, much faster, managed for high-demand analytics and can be
sparse.
+ So, BigTable(Hbase) must Column storing like C-Store for wide and sparse data.
+ In a column oriented, NULLs are much easier to handle, and impose a significantly smaller
performance overhead.
+ And supports both Horizontal/Vertical Parallel Processing.
+ 
+ Do you know RDF(Resource Description Framework) Storage?
+ We Can put it.
+ 
+  * Storing and managing very large amounts of structured data
+  * Row/column space can be sparse
+  * Columns are in the form of (family: optional qualifier). This is a RDF Properties 
+  * Columns have type information  
+  * Because of the design of the system, columns are easy to create (and are created implicitly)

+  * Column families can be split into locality groups (Ontologies!) 
+ 
+ And then, assume some job.
+ I wanna get clustered document set by one of RDF Properties.
+ It can be Readed only vertical(Column) Data from Table, because Column-stored.
+ if you are not in agreement on this point, let me show your ideas via attach me through
MSN Messenger(webmaster@udanax.org)
+ 
+ ----
+ 

Mime
View raw message