Refresh UDTs after "keyspace updated" event with v1/v2 protocol

Description

Due to CASSANDRA-7617, when using the v1/v2 protocol, schema change responses and events for UDT changes will appear as "keyspace updated" messages.

The driver should attempt to refresh its view of UDTs whenever we get an event like that and we're using the v1/v2 protocol.

Environment

None

Pull Requests

None

Activity

Show:
Adam Holmberg
August 25, 2016, 6:00 PM

I tested that locally, but I had extra types. The issue was going from one to zero types in the keyspace. Thanks for catching that.

Resolved and merged.

Greg Bestland
August 24, 2016, 4:51 PM
Edited

I think we have an issue here.

The problem where the UDT was not added to the metadata in protocol v1/v2 is fixed, but when you drop the udt, those changes are still not reflected in the metadata, with protocol v1/2. (works fine with v3/v4).

I added a test with both protocol versions here. You can run them against a version that supports protocol v1/2 and UDT's like 2.1.x. It will demonstrate the issue.

Test is located on the 106-test branch here.

https://github.com/datastax/python-driver/commit/2d8374a2b67622e940737dd101b49855c312076f

Fixed

Assignee

Greg Bestland

Reporter

Tyler Hobbs

Fix versions