You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (Jira)" <ji...@apache.org> on 2020/11/18 15:22:00 UTC
[jira] [Comment Edited] (CASSANDRA-16275) Update python driver used
by cassandra-dtest
[ https://issues.apache.org/jira/browse/CASSANDRA-16275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17234711#comment-17234711 ]
Sam Tunnicliffe edited comment on CASSANDRA-16275 at 11/18/20, 3:21 PM:
------------------------------------------------------------------------
No worries, thanks [~aholmber].
Yes, the drivers are installed during the docker image build (I guess to save time when starting the containers). They do pull the driver branch to get the latest update every time the container is launched, the thought being that this will be minimal I suppose.
I tried just updating the requirements.txt so that pip would pull a version with the V5 stuff, but the {{-w}} flag on pip update doesn't seem to remove the compiled artifacts ({{.c}} & {{.so}} objects) that were installed at build time, and there are some incompatibilities there with the latest src.
You're right that it doesn't strictly require INFRA-21103 though, it might just be a good time to start publishing to an asf namespace. If there's no movement on that ticket in the next day or two we could just go ahead and publish to an individual account.
was (Author: beobal):
No worries, thanks [~aholmber].
Yes, the drivers are installed during the docker image build (I guess to save time when starting the containers). They do pull the driver branch to get the latest update every time the container is launched, the thought being that this will be minimal I suppose.
I tried just updating the requirements.txt so that pip would pull a version with the V5 stuff, but the {{-w}} flag on pip update doesn't seem to remove the compiled artifacts ({.c} & {.so} objects) that were installed at build time, and there are some incompatibilities there with the latest src.
You're right that it doesn't strictly require INFRA-21103 though, it might just be a good time to start publishing to an asf namespace. If there's no movement on that ticket in the next day or two we could just go ahead and publish to an individual account.
> Update python driver used by cassandra-dtest
> --------------------------------------------
>
> Key: CASSANDRA-16275
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16275
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/python
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
>
> In order to commit CASSANDRA-15299, the python driver used by the dtests needs to include PYTHON-1258, support for V5 framing.
> Updating the python driver's cassandra-test branch to latest trunk causes 1 additional dtest failure in {{auth_test.py::TestAuth::test_handle_corrupt_role_data}} because the {{ServerError}} response is now subject to the configured {{retry_policy}}. This means the error ultimately returned from the driver is {{NoHostAvailable}}, rather than {{ServerError}}.
> I'll open a dtest pr to change the expectation in the test and we can commit that when the cassandra-test branch is updated.
> cc [~aholmber] [~aboudreault]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org