You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also, installing tcnative, netty, etc. is probably no longer necessary with later versions.
As a simpler short-term fix, please consider upgrading the client version and removing extra dependencies.
As a longer-term (or alternative) fix, please consider using released binaries (as per issue #1), which avoids the entire expensive build process altogether.
I'm a bit confused here. Why is the hbase distribution necessary for running opentsdb on top of bigtable? Also, why does the bigtable hbase connector need to be built separately from opentsdb? doesn't opentsdb already build asyncbigtable-0.3.0-jar-with-dependencies.jar?
I'm wondering if the instructions can just be simplified to simply download a binary distribution of opentsdb and fetch asyncbigtable-0.3.0-jar-with-dependencies.jar from mvn central?
For the short term, please:
replace bigtable-hbase-1.2-0.9.5.1.jar with bigtable-hbase-1.x-hadoop-1.5.0
I'm a bit confused here. Why is the hbase distribution necessary for running opentsdb on top of bigtable? Also, why does the bigtable hbase connector need to be built separately from opentsdb? doesn't opentsdb already build asyncbigtable-0.3.0-jar-with-dependencies.jar?
I'm wondering if the instructions can just be simplified to simply download a binary distribution of opentsdb and fetch asyncbigtable-0.3.0-jar-with-dependencies.jar from mvn central?
Yes, that's what I am proposing separately in issue #1. This is suggesting a possibly easier, shorter-term fix to use a newer version of the library.
The current version of the
Dockerfile
says:This is installing Cloud Bigtable client
0.9.5.1
, which is quite old: the latest release of Cloud Bigtable client, as of this writing, is1.5.0
.Also, installing tcnative, netty, etc. is probably no longer necessary with later versions.
As a simpler short-term fix, please consider upgrading the client version and removing extra dependencies.
As a longer-term (or alternative) fix, please consider using released binaries (as per issue #1), which avoids the entire expensive build process altogether.
/cc: @sduskis, @igorbernstein2, @ghaisa (FYI)
The text was updated successfully, but these errors were encountered: