[ 
https://issues.apache.org/jira/browse/KNOX-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746435#comment-16746435
 ] 

Dequan Chen commented on KNOX-1237:
-----------------------------------

 [~risdenk]:

The implementation of the Knox Shell HBase stateless scanner is to use a 
temporary stateful scanner ID to get all the data of a user's request by >=1 
step(s) and return the complete data to the user depending on the request 
(version #, columns, rows etc). So the user does not need to create any 
stateful scanner(s) to loop through all possible steps for each step's data + 
combining the data as a whole.... Therefore, the user does not see any stateful 
scanner action because of the encapsulation adopted in the object-oriented 
implementation. Hope that the explanation helps you understand that.

Dequan

1/18/2019

 

> Knox DSL should support HBase Stateless Scanner
> -----------------------------------------------
>
>                 Key: KNOX-1237
>                 URL: https://issues.apache.org/jira/browse/KNOX-1237
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: ClientDSL
>            Reporter: Kevin Risden
>            Assignee: Dequan Chen
>            Priority: Minor
>             Fix For: 1.3.0
>
>         Attachments: KNOX-1237.patch, KNOX-1237.patch
>
>
> KNOX-8 added support for HBase REST apis via Knox. The Knox DSL supports 
> stateful scanners as shown in the documentation 
> (https://knox.apache.org/books/knox-1-0-0/user-guide.html#table(String+tableName).scanner().create()+-+Scanner+Creation).
> HBase REST supports stateless scanners 
> ([https://hbase.apache.org/1.2/apidocs/org/apache/hadoop/hbase/rest/package-summary.html#operation_stateless_scanner])
>  which can be easily load balanced. The feature is not well documented in 
> HBase REST.
> Currently if using stateful scanners and Knox or HBase REST is being load 
> balanced, there will be an issue using that scanner. The stateless scanners 
> avoid this since they have all the information necessary.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to