-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
ycsb launcher should only include binding specific jars in the classpath #302
Comments
That's what seems to be happening with the current launcher. For instance, when running a HBase workload, the following jars are included in the classpath: Perhaps this was different in the launcher before a recent change? |
that's with the pre-#300 launcher? or with the current launcher in the hbase dist tarball? or with the current launcher in the everything-dist tarball? |
This was the current launcher, but I had changed the pom.xml to build only HBase. Reverting it to build everything still includes only the core and hbase-binding jars (but all conf directories -- that could be fixed, if needed): .../ycsb-0.2.0-SNAPSHOT/gemfire-binding/conf:.../ycsb-0.2.0-SNAPSHOT/core/lib/core-0.2.0-SNAPSHOT.jar:.../ycsb-0.2.0-SNAPSHOT/voldemort-binding/conf:.../ycsb-0.2.0-SNAPSHOT/tarantool-binding/conf:.../ycsb-0.2.0-SNAPSHOT/jdbc-binding/conf:.../ycsb-0.2.0-SNAPSHOT/accumulo-binding/conf:.../ycsb-0.2.0-SNAPSHOT/hbase-binding/conf:.../ycsb-0.2.0-SNAPSHOT/hbase-binding/lib/hbase-binding-0.2.0-SNAPSHOT.jar |
This is biting me - |
Thinking about this more, I think this is a regression . before the @gkamat, will you have time to work through this soon? If not, would you
|
Commit 2559ce6 should fix this. Had some issues rebasing, but the change to bin/ycsb is all that is needed. |
closes brianfrankcooper#302 ycsb launcher should only include binding specific jars in the classpath
closes brianfrankcooper#302 ycsb launcher should only include binding specific jars in the classpath
right now when you use the ycsb launcher, we build a classpath with all the jars from all the bindings.
instead, find_jars should build a classpath with just the core libraries (in lib/) and those for the selected binding (in datastore-binding/lib as of #300)
The text was updated successfully, but these errors were encountered: