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 stack
Date Wed, 21 Nov 2007 20:18:08 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:
Note agreement on how we'll do timestamps for now.

  This is a provisional spec for the Hbase-REST API done under the aegis of [https://issues.apache.org/jira/browse/HADOOP-2068
+ Below XML illustrations use XML entities heavily.  Actual implementation doesn't use entities
at all (TODO: Update examples).
  == System Information ==
@@ -16, +18 @@

- ~-''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
  '''GET /[table_name]'''
      Retrieve metadata about the table. This includes column family descriptors.
@@ -70, +71 @@

  ~-''St.Ack comment 11/17/2007: What is this time format?  Want to do ISO 8601?  Should be
fixed size, milliseconds?  Or flexible about timestamp format?-~
  ~-''Bryan comment 11/19/2007: What kind of granularity do we have for timestamps in HBase?
I'm open to pretty much whatever standard we choose, so long as the granularity matches. I
do think we should choose a specific format - there's really no benefit to flexible formats.
+ ~-''St.Ack comment: Chatting w/ Bryan on IRC, lets just return the long the hbase server
supplies in a String format for now.''-~
  '''GET /[table_name]/row/[row_key]/'''

View raw message