You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Risden (JIRA)" <ji...@apache.org> on 2019/01/18 15:41:00 UTC

[jira] [Commented] (KNOX-1237) Knox DSL should support HBase Stateless Scanner

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

Kevin Risden commented on KNOX-1237:
------------------------------------

[~dequanchen] while looking through the patch I see the following line

while (!(tempValue = HBase.session(session).table(tableName).scanner(scannerId).getNext().now().getString()).isEmpty()) { +

 

This looks like it creates a stateful scanner from within the stateless scanner? That doesn't seem correct to me. There should be no reason to have any Scanner ID from within the stateless scanner.

> 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)