12-23-2015 05:59 AM - edited 12-23-2015 06:02 AM
I'm running into a trouble when trying to create an Java based client which is used to query data from both Cloudera HBase 1.0.0 (CDH 5.4.7) and ElasticSearch 2.1.0. The issue is about dependency conflicts on guava library.
This bug describes exactly the same issue as I met:
At least in my case using explicity a lower versio of guava (lower than 17.0 from where the breaks happens) is out of the table because it will lead Elasticsearch JAVA search API failure. And now I'm trying the Apache HBase Shaded Client 1.1.2 (which is designed for HBase 1.1.0 I suppose), at least so far some of the simple HBase operations (I tried only get/scan so far) are all suceeded.
I'm wondering if there is any known risk or issue about using Apache HBase Shaded Client 1.1.x with CDH Hbase 1.0.0?
I need to understand this because we are considering using this solution in production enviroment very soon.
Your helps will be much apprecated!
12-25-2015 11:20 PM
Not sure why my previous reply to this thread got lost....
So far we've tried GET/SCAN/PUT with reasonable load and all of them works in our environment (shad cliet 1.1.2 + HBase 1.0.0). It should be sufficient for our requirement so far.
But it's still good to understand what is the design rules for Hadoop/Hbase client on backward/forward compatibilityes, so that we can evaluate the necessary of upgrading all of our applications based on Hadoop/Hbase client libaries, when there is any updates happnes on server end.
12-26-2015 04:57 AM
Sorry about the lost reply. For some reason it ended up getting caught in the site's spam filter. Very odd.
07-19-2016 04:08 PM
I am facing the same issue, Even after applying all the suggestion no luck.
I am using Hbase 1.0.0 and ElasticSearch 2.3.4 In Spark-scala built using sbt.
Any pointer highly appreciated.
07-28-2016 06:29 PM