[
https://issues.apache.org/jira/browse/CASSANDRA-18960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783182#comment-17783182
]
Andres de la Peña commented on CASSANDRA-18960:
-----------------------------------------------
Good catch. The driver's
[{{README}}|https://github.com/datastax/python-driver/blob/7845379b61fd50d4c3d6f20b215454f3d74d2c28/README.rst]
says it only supports 3.7 and 3.8. However CI's tests for cqlsh run (and pass)
with Python 3.7, 3.8 and 3.11. I'll investigate the situation about supported
versions to see if we need to change the requirements and the CI jobs.
> Upgrade Python driver to 3.28.0
> -------------------------------
>
> Key: CASSANDRA-18960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18960
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Vector Search, Tool/cqlsh
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 5.0-alpha3, 5.0, 5.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The version of the Python driver that is used by cqlsh (3.25.0) doesn't
> entirely support the new vector data type introduced by CASSANDRA-18504.
> While we can perfectly write data, read vectors are presented as blobs:
> {code}
> > CREATE TABLE t (k int PRIMARY KEY, v vector<int, 2>);
> > INSERT INTO t(k, v) VALUES (0, [1, 2]);
> > SELECT * FROM t;
> k | v
> ---+-------------------------------------
> 0 | b'\x00\x00\x00\x01\x00\x00\x00\x02'
> {code}
> I think that would we fixed if we update the driver to (at least) 3.28.0,
> which includes support for the new vector data type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
