Dear Wiki user,

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

The following page has been changed by sishen:
http://wiki.apache.org/hadoop/Hbase/HbaseRest

------------------------------------------------------------------------------
      Create a table.    
      Headers:
          Content-type:
-             application/xml:    The client is sending the table metadata in 
an XML entity.
+             text/xml:    The client is sending the table metadata in an XML 
entity.
      Returns:
          HTTP 200 (OK) if the table could successfully be created.
      
@@ -83, +83 @@

     Update the table schema.
      Headers:
          Content-type:
-             application/xml:    The client is sending the table metadata in 
an XML entity.
+             text/xml:    The client is sending the table metadata in an XML 
entity.
      Returns:
          HTTP 200 (OK) if the table could successfully be updated.
  
@@ -142, +142 @@

  
      Headers:
          Accept:
-             application/xml:    The client is expecting an XML entity body 
that contains the 
+                      text/xml:  The client is expecting an XML entity body 
that contains the 
                                  columns and data together.
              
              Multipart/related:  The client is expecting raw binary data, but 
organized into a 
                                  multipart response. The client must be 
prepared to parse the 
-                                 column values out of the data.
+                                 column values out of the data. not supported 
yet.
  
      Parameters:
          column: specify one or more column parameters (&-separated) to get 
the content of specific cells. If omitted, the result will contain all columns 
in the row.
@@ -161, +161 @@

  
      Headers:
          Content-type:
-             application/xml:    The client is sending one or more columns of 
data in an XML entity.
+                      text/xml:  The client is sending one or more columns of 
data in an XML entity. The column value must be base64 encoded.
  
-             Multipart/related:  The client is sending multiple columns of 
data encoded with boundaries.
+             Multipart/related:  The client is sending multiple columns of 
data encoded with boundaries. Not supported yet.
              
      Parameters:
          column: specify one or more column parameters (&-separated) to get 
the content of specific cells. If omitted, the result will contain all columns 
in the row.
@@ -186, +186 @@

      Returns:
          HTTP 202 (Accepted) if the column(s) were deleted.
  
+ ~-''sishen comment: Delete based on timestamp currently not supported yet but 
we need implement it-~
      
  == Scanning ==
  
@@ -212, +213 @@

      
      Headers:
          Accept:
-             application/xml:    The client is expecting an XML entity body 
that contains the 
+                      text/xml:  The client is expecting an XML entity body 
that contains the 
                                  columns and data together.
  
              Multipart/related:  The client is expecting raw binary data, but 
organized into a 
                                  multipart response. The client must be 
prepared to parse the 
-                                 column values out of the data.
+                                 column values out of the data. Not supported 
yet.
+     Parameters:
+         limit: return N numbers of items
      Returns:
          HTTP 200 (OK) and an entity that describes the current row in the 
scanner. The entity value of this request 
          depends on the Accept header. See the documentation for getting an 
individual row for data format.

Reply via email to