Oleksandr Luzhniy
Oleksandr Luzhniy
Hello! I will try to handle it.
> Hello! I will try to handle it. During the implementation of the vector type support I found several issues: - The Vector type is implemented in Cassandra as not...
> > The Vector type is implemented in Cassandra as not the native collection type but the custom type. > > Could this be because gocql uses [protocol v4](https://github.com/apache/cassandra/blob/df78296dcbc67c1d6dd1e0412fcd71f0a8f8fa7c/doc/native_protocol_v4.spec), which...
> @tengu-alt, could you take a look at it? I'll handle it.
Made some updates: refactored tests, added new logic(`refreshRing()` from now does NOOP when `DisableInitialHostLookup` is true), and refactored code according to feedback. Also fixed the conflicts .
@joao-r-reis Could you please take a look?
> I have an alternative solution that I can propose soon without depending on any other PRs. Sounds good, let's see it when it arrives.
Have you tested it with protoV5? If not I would be glad to handle it with #1822.
Overall, looks good to me, except [this](https://github.com/apache/cassandra-gocql-driver/pull/1828?notification_referrer_id=NT_kwDOBPXNN7QxMjgwMDgzMDIyOTo4MzIxNzcxOQ#discussion_r2034742664) and [this](https://github.com/apache/cassandra-gocql-driver/pull/1828?notification_referrer_id=NT_kwDOBPXNN7QxMjgwMDgzMDIyOTo4MzIxNzcxOQ#discussion_r2034129465).
@gouthamve UDT does not support `omitempty` tag, all fields must exist, so I think there is no sense in implementing support for it. gocql itself will overwrite non-filled values by...