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] Trivial Update of "Hbase/HbaseRest" by stack
Date Thu, 15 Nov 2007 19:29:37 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 stack:
http://wiki.apache.org/lucene-hadoop/Hbase/HbaseRest

The comment on the change is:
Minor formatting and replies to Bryans' remarks.

------------------------------------------------------------------------------
  ~-''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.''-~
+ 
+ ~-''St.Ack comment 11/15/2007: OK -~ 
  
  == Row Interaction ==
  
@@ -108, +110 @@

  
  ~-''Bryan comment: While we certainly could use headers, I'd prefer not to. Headers seem
like an ugly way to say what you're sending. In REST, you're supposed to specify '''what'''
you're acting on in the URI, not headers, and which columns to save to qualifies to me. It
may turn out to be an implementation question, but we'll see. ''-~
  
+ 
+ ~-''St.Ack comment 11/15/2007: I agree -~ 
+ 
      
  '''DELETE /[table_name]/row/[row_key]/'''
  '''DELETE /[table_name]/row/[row_key]/[timestamp]'''
@@ -120, +125 @@

          HTTP 202 (Accepted) if the column(s) were deleted.
  
      
- == Scanning ==    
+ == Scanning ==
  
  '''POST/PUT /[table_name]/scanner'''
      Request that a scanner be created with the specified options. Returns a scanner ID that
can be used to iterate over the results of the scanner.
@@ -171, +176 @@

  ~- Stack comment: DELETE to increment strikes me as wrong.  What about a POST/PUT to the
URL /[table_name]/scanner/[scanner_id]/next?  Would return current and move scanner to next
item? -~
  
  ~- Bryan comment: Unforunately I don't think there is any good HTTP verb for this operation.
DELETEing /current is about as good as POST/PUTing /next. With the DELETE approach, there
is one less resource, though. -~
+ 
+ ~-''St.Ack comment 11/15/2007: Can you explain 'one less resource'?  (I'm dumb, remember).
 Maybe DELETE ain't that bad.  We might also try and solicit other opinions on this point.
-~ 
      
  '''DELETE /[table_name]/scanner/[scanner_id]'''
      Close a scanner. You must call this when you are done using a scanner to deallocate
it.

Mime
View raw message