Re: Provide storage which use HBase's native client(not Asynchbase).

Following a month-old discussion, I don’t think Asynchbase 1.7.1 supports the operation-level RPC timeout, and the related issue #11 is being delayed from v1.5.0 to v1.8.0, so we never know, how it would happen, unless we decide to contribute

Re: Provide storage which use HBase's native client(not Asynchbase).

Thanks for suggestions Jong Wook. I think shading would solve version conflict problems. I am not familiar with this issue. Jong Wook, can you contribute your knowledge on shading? I think we should make sure discuss on version conflict problems regardless native client storage providing. so it

Re: Provide storage which use HBase's native client(not Asynchbase).

It seems like Elasticsearch had similar problems: https://www.elastic.co/blog/to-shade-or-not-to-shade On Wed, Apr 20, 2016 at 10:36 AM Jong Wook Kim wrote: > As per Guava version conflict, we should be able to shade the dependency > to another package, maybe with the whole