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 ------------------------------------------------------------------------------ XML entity body that describes the list of available timestamps: {{{ <timestamps> - <timestamp value="20071115T000000" uri="/first_table/row/0001/20071115T000000" /> + <timestamp value="20071115T000000" uri="/first_table/row/0001/198123908129038419083" /> - <timestamp value="20071115T000800" uri="/first_table/row/0001/20071115T000800" /> + <timestamp value="20071115T000800" uri="/first_table/row/0001/108293471089237018937" /> - <timestamp value="20071115T001200" uri="/first_table/row/0001/20071115T001200" /> + <timestamp value="20071115T001200" uri="/first_table/row/0001/019823701983981731089" /> </timestamps> }}} @@ -156, +156 @@ Returns: HTTP 201 (Created) with a Location header that references the scanner URI. Example: - /first_table/scanner/1234348890231890 + /first_table/scanner?timestamp=1234348890231890&column=colfam1:name&start_key=first_key&end_key=last_key ~-''St.Ack comment 11/18/2007: I added timestamp parameter. Should start_key, end_key, OR timestamp be on the URL path to sync. with how they are specified GET'ing, etc?-~ - + - '''GET /[table_name]/scanner/[scanner_id]/current''' + '''POST /[table_name]/scanner/[scanner_id]''' + Return the current item in the scanner and advance to the next one. Think of it as a queue dequeue operation. - Get the row and columns for the current item in the scanner without advancing the scanner. - Equivalent to a queue peek operation. Multiple requests to this URI will return the same result. Headers: Accept: @@ -178, +177 @@ depends on the Accept header. See the documentation for getting an individual row for data format. If the scanner is used up, HTTP 404 (Not Found). - - '''DELETE /[table_name]/scanner/[scanner_id]/current''' - Return the current item in the scanner and advance to the next one. Think of it as a queue dequeue operation. - - Headers: - Accept: - application/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. - 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. - - If the scanner is used up, HTTP 404 (Not Found). ~- 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? -~
