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 Sun, 18 Nov 2007 22:16:40 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:

The comment on the change is:
Further comment on how scanners should work

  ~- Bryan comment: What I mean is that instead of supporting two separate verbs to two different
URIs (/current and /next) there would be only one URI with two verbs. Additionally, after
some more thought, I think DELETE would be better because it implies that something is being
consumed or deleted, as opposed to POST/PUT which sort of imply something new is being created.
Again, though, I think it is a bit of hair splitting, seeing as how the HTTP spec is going
to have to be bent a little to work right for this particular request anyways (DELETE or POST/PUT
shouldn't usually return an entity-body, and we will want it to so that we don't have to make
two separate requests, one for getting the current and another for advancing it). -~
+ ~-''St.Ack comment 11/18/2007: Trying to implement, the 'current' tail on a resource URI
doesn't add any value GET'ing; what else but the 'current' record would you be GETing. A GET
on a URI that ends in a scannerid is enough to figure whats wanted.  If this is allowed, given
that below a delete on a URI that ends in a scannerid closes the scanner, I would suggest
that a PUT/POST on an URI that ends in a scannerid is the way to advance it (returning current
  '''DELETE /[table_name]/scanner/[scanner_id]'''
      Close a scanner. You must call this when you are done using a scanner to deallocate

View raw message