[
https://issues.apache.org/jira/browse/S2GRAPH-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537461#comment-15537461
]
ASF GitHub Bot commented on S2GRAPH-116:
----------------------------------------
Github user SteamShon commented on the issue:
https://github.com/apache/incubator-s2graph/pull/85
@jongwook
I have checkout this PR and run `sbt test`, then I got following errors.
It seems like ByteBuddy needs some more setup. Please give me help if I
missed something.
```
[info] Exception encountered when attempting to run a suite with class
name: org.apache.s2graph.core.ManagementTest *** ABORTED *** (127 milliseconds)
[info] java.lang.NoClassDefFoundError: Could not initialize class
org.apache.s2graph.core.storage.hbase.AsynchbaseStorage$
[info] at
org.apache.s2graph.core.storage.hbase.AsynchbaseStorage.<init>(AsynchbaseStorage.scala:95)
```
> 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)
