-
Notifications
You must be signed in to change notification settings - Fork 34
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
remove cassandra from the shiv package #96
Conversation
f86f531
to
3dfd7f8
Compare
It's a good idea to have fewer versions of the driver. |
I don't like the idea of every change or fix we'll want to the cqlsh, it won't go via new dbuild image... |
so we can use the scylla-python3 driver version the only problem now, we depend on new dbuild version for using newer version of scylla-driver with cqlsh. it's really slow down the ability to update new feature that depends on new driver chanages (not too many of those) Depends: scylladb/scylla-python3#40 Fixes: scylladb#95
The python driver is also used for the tests, so it's a good idea to keep it updated. |
The alternative is to include the python driver as a submodule and build it as part of the build process. |
an alternative is todo exactly what scylla-python3 is doing for the downloaded wheel (without submoduling anything), i.e. patchelf the files, I think it would work exactly as the driver from scylla-python3 works. it just gonna take time to build it and try it out, and confirm it's working. I'm still trying to completely build this one in: |
Passed complication and gating tests @syuu1228, can you review this change ? |
The submodule is a solution to having to regenerate the frozen toolchain on each driver change. Since the driver changes often, and is part of our source base, it's reasonable to build it as part of the build process. |
I found that there are more shared library on shiv, it may cause similar error since these are not relocatable binaries:
I saw previous discussion on the thread we should use scylla-driver on scylla-python3 or install specific version of scylla-driver, here are example code on both versions.
|
@syuu1228 we can put the |
Meanwhile we'll deliver this change to unblock master, as it was proven to be working in: I'll try out the change of patching the .so in the shiv zip, without depending on the driver in scylla-python3 |
* tools/cqlsh 73bdbeb0...86a280a1 (1): > remove cassandra from the shiv package Ref: scylladb/scylla-cqlsh#96
* tools/cqlsh 73bdbeb0...86a280a1 (1): > remove cassandra from the shiv package Ref: scylladb/scylla-cqlsh#96 Closes #19558
so we can use the scylla-python3 driver version
the only problem now, we depend on new dbuild version for using newer version of scylla-driver with cqlsh.
it's really slow down the ability to update new feature that depends on new driver changes (not too many of those)
Ref: scylladb/scylla-python3#40
Fixes: #95