Bug
Prepared statements that reference a user-defined type can remain cached after that UDT is altered.
The cache invalidation code compares the changed UDT with prepared statement metadata using full UDT equality. After an ALTER TYPE, result or variable metadata may contain the same keyspace/type name with a different field definition. Because full equality includes the field definitions, the driver can fail to recognize that the prepared statement depends on the changed UDT.
Impact
A prepared statement can continue to be reused even though its referenced UDT schema changed. This is especially visible for statements whose result or variable metadata contains UDTs nested in collections, tuples, or other UDTs.
Expected Behavior
When a UDT changes, cached prepared statements that reference that UDT should be invalidated based on the UDT identity: keyspace and type name.
Bug
Prepared statements that reference a user-defined type can remain cached after that UDT is altered.
The cache invalidation code compares the changed UDT with prepared statement metadata using full UDT equality. After an
ALTER TYPE, result or variable metadata may contain the same keyspace/type name with a different field definition. Because full equality includes the field definitions, the driver can fail to recognize that the prepared statement depends on the changed UDT.Impact
A prepared statement can continue to be reused even though its referenced UDT schema changed. This is especially visible for statements whose result or variable metadata contains UDTs nested in collections, tuples, or other UDTs.
Expected Behavior
When a UDT changes, cached prepared statements that reference that UDT should be invalidated based on the UDT identity: keyspace and type name.