You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Nicolas Liochon (JIRA)" <ji...@apache.org> on 2015/02/25 10:38:05 UTC

[jira] [Created] (HBASE-13099) Scans as in DynamoDB

Nicolas Liochon created HBASE-13099:
---------------------------------------

             Summary: Scans as in DynamoDB
                 Key: HBASE-13099
                 URL: https://issues.apache.org/jira/browse/HBASE-13099
             Project: HBase
          Issue Type: Brainstorming
          Components: Client, regionserver
            Reporter: Nicolas Liochon


cc: [~saint.ack@gmail.com] - as discussed offline.

DynamoDB has a very simple way to manage scans server side:
??citation??
The data returned from a Query or Scan operation is limited to 1 MB; this means that if you scan a table that has more than 1 MB of data, you'll need to perform another Scan operation to continue to the next 1 MB of data in the table.

If you query or scan for specific attributes that match values that amount to more than 1 MB of data, you'll need to perform another Query or Scan request for the next 1 MB of data. To do this, take the LastEvaluatedKey value from the previous request, and use that value as the ExclusiveStartKey in the next request. This will let you progressively query or scan for new data in 1 MB increments.

When the entire result set from a Query or Scan has been processed, the LastEvaluatedKey is null. This indicates that the result set is complete (i.e. the operation processed the “last page” of data).
??citation??

This means that there is no state server side: the work is done client side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)