-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[hbase20] no slf4j implementation; hbase client doesn't log #1173
Comments
Closed
As a workaround, you can download the slf4j simple logger directly: e.g. for the hbase 2.0 specific tarball:
for 0.15.0 you'd end up with
similarly, for the full YCSB tarball:
for 0.15.0 you'd end up with
|
Closed
busbey
added a commit
to busbey/YCSB
that referenced
this issue
Feb 3, 2020
* remove 0.98, 1.0, 1.2, and 2.0 bindings * add 2.2 binding * incorporate README from 0.98 binding into current bindings * incorporate README on bigtable testing from 1.0 binding into 1.4 binding * incorporate implementation from 1.0 client into current bindings * updated asynchbase binding to include parts of removed bindings it referenced * update 1.4 and 2.2 to current releases * use shaded client test for all hbase bindings. * make hbase bindings consistently use log4j * fixes brianfrankcooper#1173 * fixes brianfrankcooper#1172
busbey
added a commit
to busbey/YCSB
that referenced
this issue
Feb 3, 2020
* remove 0.98, 1.0, 1.2, and 2.0 bindings * add 2.2 binding * incorporate README from 0.98 binding into current bindings * incorporate README on bigtable testing from 1.0 binding into 1.4 binding * incorporate implementation from 1.0 client into current bindings * updated asynchbase binding to include parts of removed bindings it referenced * update 1.4 and 2.2 to current releases * use shaded client test for all hbase bindings. * make hbase bindings consistently use log4j * fixes brianfrankcooper#1173 * fixes brianfrankcooper#1172
busbey
added a commit
to busbey/YCSB
that referenced
this issue
Feb 3, 2020
* remove 0.98, 1.0, 1.2, and 2.0 bindings * add 2.2 binding * incorporate README from 0.98 binding into current bindings * incorporate README on bigtable testing from 1.0 binding into 1.4 binding * incorporate implementation from 1.0 client into current bindings * updated asynchbase binding to include parts of removed bindings it referenced * update 1.4 and 2.2 to current releases * use shaded client test for all hbase bindings. * make hbase bindings consistently use log4j * fixes brianfrankcooper#1173 * fixes brianfrankcooper#1172
busbey
added a commit
that referenced
this issue
Feb 5, 2020
* remove 0.98, 1.0, 1.2, and 2.0 bindings * change the 1.4 binding to be a "HBase 1.y" binding * add "HBase 2.y" binding and default it to the current 2.2 release * incorporate README from 0.98 binding into current bindings * incorporate README on bigtable testing from 1.0 binding into 1.4 binding * incorporate implementation from 1.0 client into current bindings * updated asynchbase binding to include parts of removed bindings it referenced * update maprdb binding for the change in the hbase bindings * update 1.4 and 2.2 to current releases * use shaded client test for all hbase bindings. * make hbase bindings consistently use log4j * fixes #1173 * fixes #1172
Looks like the maven.org has a redirect, using -L gets to the actual jar. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
running through testing the
hbase20
binding, there's no logs from the client library (as there are in the earlier bindings).Looks like the hbase 1.2 and hbase 1.4 shaded jars incorrectly included a dependency on the
slf4j-log4j12
bridge. so to have the same logging on the hbase 2.0 client we'll need to add it.The text was updated successfully, but these errors were encountered: