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/HbaseRest" by BryanDuxbury
Date Thu, 15 Nov 2007 18:46:13 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 BryanDuxbury:
http://wiki.apache.org/lucene-hadoop/Hbase/HbaseRest

------------------------------------------------------------------------------
      
      Returns: 
          XML entity body that contains a list of the tables like so:
-         <tables>
+ {{{
+ <tables>
-             <table name="first_table" uri="/first_table" />
+   <table name="first_table" uri="/first_table" />
-             <table name="second_table" uri="/second_table" />        
+   <table name="second_table" uri="/second_table" />        
-         </tables>
+ </tables>
+ }}}
+ 
  ~-''St.Ack comment: FYI, there is an xhtml formatter in hbase under the shell package. 
If we used that for outputting metadata-type pages such as this one, then we'll have a legup
on implementation.  It uses xmlenc which is bundled w/ hadoop.  xmlenc is fast and dumb (like
me).  IIRC, it doesn't do entities; it adds the entity to the closer element too.  This is
dumb.  On otherhand, it makes it so we don't have to have the entities vs. elements argument
(Smile).''-~
      
  '''GET /[table_name]'''
@@ -22, +25 @@

  
      Returns: 
          XML entity body that contains all the metadata about the table:
-         <table>
+ {{{
+ <table>
-             <columnFamilies>
+   <columnFamilies>
-                 <columnFamily name="meta" />
+      <columnFamily name="meta" />
-                 <columnFamily name="content" />
-                 <columnFamily name="stats" />
+        <columnFamily name="content" max-versions=3 compression="NONE" in-memory="false"
max-length=2147483647 bloom-filter="none" />
+        <columnFamily name="stats" max-versions=3 compression="NONE" in-memory="false"
max-length=2147483647 bloom-filter="none" />
-             </columnFamilies>
+      </columnFamilies>
-         </table>
+ </table>
+ }}}
+ 
  ~-''St.Ack comment: FYI, here is an example column descriptor: {name: triples, max versions:
3, compression: NONE, in memory: false, max length: 2147483647, bloom filter: none}.  We're
also about to add being able to add arbitrary key/value pairs to both table and column descriptors-~
   
  
  '''GET /[table_name]/regions'''
@@ -38, +44 @@

          start_key, end_key: Only return the list of regions that contain the range start_key...end_key
      Returns: 
          XML entity body that describes the regions:
-         <regions>
-             <region start_key="0001" server="region_server_1" />
-             <region start_key="0101" server="region_server_2" />
-             <region start_key="0201" server="region_server_3" />
-         </regions>
  
+ {{{
+ <regions>
+   <region start_key="0001" server="region_server_1" />
+   <region start_key="0101" server="region_server_2" />
+   <region start_key="0201" server="region_server_3" />
+ </regions>
+ }}}
+ 
- ~-''St.Ack comment: This won't be needed if you use TableInputFormat in your mapper -- but
no harm in having it in place-~   
+ ~-''St.Ack comment: This won't be needed if you use TableInputFormat in your mapper -- but
no harm in having it in place''-~
+ 
+ ~-''Bryan comment: Only if you're using the Hadoop MapReduce. We've got our own.''-~
  
  == Row Interaction ==
  

Mime
View raw message