[
https://issues.apache.org/jira/browse/CASSANDRA-18960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784483#comment-17784483
]
Brad Schoening edited comment on CASSANDRA-18960 at 11/9/23 2:42 PM:
---------------------------------------------------------------------
Perfect is the enemy of good sometimes. Maybe just bump the minimum to 3.7 for
now. That would align the minimum with the driver. It would be unwise to
reject 3.9+ which had previously been supported and the documentation and code
only check the minimum.
was (Author: bschoeni):
Maybe just bump the minimum to 3.7 for now. It would be unwise to reject 3.9+
which had previously been supported and the documentation and code only check
the minimum.
> 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-beta1, 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]
