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 would be better to open up separate thread to discuss it. What do you guys think?
As you mentioned, with Native HBase client is all blocking API and What we end up easily would be enclose blocking API with Scala's Future. I was wondering if there would be anyone who want to use HBase native client rather than asynchbase, but since s2graph public interfaces are all asynchronous, I think there is any benefit to use blocking native client. So you guys are on not provide native client storage? I am +1 on providing it since it is easy and it is always better to provide more options. What others think? Best Regards DOYUNG YOON On Thu, Apr 21, 2016 at 1:17 PM Hyunsung Jo <[email protected]> wrote: > 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 <[email protected]> wrote: > > > As per Guava version conflict, we should be able to shade the dependency > > to another package, maybe with the whole asynchbase together. Guava > > versions have been the PITA for many other projects too, and usually got > > avoided this way. > > > > If we can avoid the Asynchbase+Guava issue by shading them and the only > > interesting reason left to switch is the benchmark, it might not worth > > going back to the blocking API as it will require a whole new threading > > design. > > > > Sincerely, > > Jong Wook > > > > > > Sent from my iPhone > > > > > On Apr 19, 2016, at 9:01 PM, DO YUNG YOON <[email protected]> wrote: > > > > > > Hi All. > > > > > > Since implementing storage becomes easier(I believe), I think it is > good > > to > > > have HBaseStroage which use HBase's native client. > > > The reason I brought up this is following. > > > > > > 1. in some environment, especially specific Hadoop and Spark cluster > > > distribution, > > > s2core have guava version conflict which comes from asynchbase. > > > - Many cases it is necessary to process stream of edges and write into > > > HBase directly on streaming processing. > > > - Currently, there is no way to specify version to avoid above > problem. > > > With Native HBaseClient, users will be select right version for there > > > environment. > > > 2. It would be fun to run benchmark on these two client. > > > > > > any feedback would be appreciated. > > > > > > Best Regards. > > > DOYUNG YOON > > >
