[jira] [Commented] (S2GRAPH-116) Use the official Asynchbase release and stop managing our custom fork

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on S2GRAPH-116:
----------------------------------------

Github user jongwook commented on the issue:

    https://github.com/apache/incubator-s2graph/pull/85
  
    @SteamShon Oops, my bad. There was an error occurring during the initialization of `object AsynchbasePatcher`. Just made an amended commit that includes the fix. 


> Use the official Asynchbase release and stop managing our custom fork
> ---------------------------------------------------------------------
>
>                 Key: S2GRAPH-116
>                 URL: https://issues.apache.org/jira/browse/S2GRAPH-116
>             Project: S2Graph
>          Issue Type: Improvement
>            Reporter: Jong Wook Kim
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Currently we are using our custom version of Asynchbase (at https://github.com/SteamShon/asynchbase ) for the non-blocking access to HBase servers, because of the two minor but essential missing features of the upstream Asynchbase:
> 1. to set store_limit and store_offset in GetRequests
> 2. to set the rpc-level timeout values in Scanners
> During the recent discussion in the dev mailing list we've found that the former can be replaced with ColumnPaginationFilter, and the latter we can workaround using ASM and ByteBuddy.
> This will remove the operational cost of managing a separate fork of Asynchbase as well as dealing with the separate release cycle to Maven central.



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