If a transform forces a SELECT response that includes a UDT to be reencoded, the encoded bytes will be invalid.
See #1928 for a reproduction of the issue.
To complete this ticket, we will need to write integration tests for UDT's which involves extending our CassandraConnection type to support UDTs.
CassandraConnection abstracts over 4 different drivers to allow running integration tests across all of these drivers.
If any of these drivers does not support UDT's or it is otherwise impractical to implement we can leave the implementation for that driver as a panic!() and skip over that section of the test for that driver.
Then, since these integration tests will fail, we will need to add support for UDT's to shotovers cassandra encoding (and maybe decode) implementations. This may involve upstreaming changes to https://github.com/krojew/cdrs-tokio/tree/master/cassandra-protocol
Do not pick this up as your first ticket as it is fairly involved.
If a transform forces a SELECT response that includes a UDT to be reencoded, the encoded bytes will be invalid.
See #1928 for a reproduction of the issue.
To complete this ticket, we will need to write integration tests for UDT's which involves extending our CassandraConnection type to support UDTs.
CassandraConnection abstracts over 4 different drivers to allow running integration tests across all of these drivers.
If any of these drivers does not support UDT's or it is otherwise impractical to implement we can leave the implementation for that driver as a
panic!()and skip over that section of the test for that driver.Then, since these integration tests will fail, we will need to add support for UDT's to shotovers cassandra encoding (and maybe decode) implementations. This may involve upstreaming changes to https://github.com/krojew/cdrs-tokio/tree/master/cassandra-protocol
Do not pick this up as your first ticket as it is fairly involved.