Registered classes for UDTs doesn't work in some cases

Description

A user on IRC reported issues with registering classes for UDTs. To investigate, I created a keyspace, user-defined type, and table like so:

and then tested out registering a class for the UDT:

Unexpectedly, the UDT values come back as named tuples. It doesn't seem to make a difference if the statement is prepared or not. What's strange is that tests/integration/standard/test_udts.py covers this and the tests pass.

Environment

None

Pull Requests

None

Activity

Show:
Adam Holmberg
May 1, 2015, 1:48 PM

I can add a warning for 2.6. The real answer is protocol version negotiation. There are a number of problems that come up when using C* 2.1 features with protocol version 2.

Adam Holmberg
May 14, 2015, 3:28 PM
Tyler Hobbs
May 22, 2015, 6:51 PM

+1

Adam Holmberg
May 26, 2015, 4:39 PM

I don't view this as an important thing to write an automated test around. I think it should be sufficient to run a quick one-time manual test.

Adam Holmberg
May 26, 2015, 5:55 PM

Tested by connecting and registering a type with protocol_version 2, then 3.

Verified that expected warning is output when connected with v2.

Fixed

Assignee

Adam Holmberg

Reporter

Tyler Hobbs

Fix versions

Labels

None

PM Priority

None

External issue ID

None

Doc Impact

None

Reviewer

None

Size

None

Pull Request

None

Priority

Minor
Configure