[
https://issues.apache.org/jira/browse/CASSANDRA-9960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659796#comment-14659796
]
Jaroslav Kamenik commented on CASSANDRA-9960:
---------------------------------------------
I have found this problem using datastax java client. I have used select from
system.schema_usertypes to check if I need to create type (i know, there is IF
NOT EXIST clause:). Sometimes it said 'type is there', just after drop/create
whole keyspace. Drop/create was made before my java app started, so it does not
seem to be problem of client caches or so... I checked it in CQLSH (it was
started after this problem happened), where
select * from system.schema_usertypes
returned nothing, but
select * FROM system.schema_usertypes WHERE keyspace_name='ks' AND
type_name='typename';
returned type definition.
It started after the upgrade to C* 2.2.
> UDTs still visible after drop/recreate keyspace
> -----------------------------------------------
>
> Key: CASSANDRA-9960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9960
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jaroslav Kamenik
> Priority: Critical
>
> When deploying my app from the scratch I run sequence - drop keyspaces,
> create keyspaces, create UDTs, create tables, generate lots of data... After
> few cycles, randomly, cassandra ends in state, where I cannot see anything in
> table system.schema_usertypes, when I select all rows, but queries with
> specified keyspace_name and type_name return old values. Usually it helps to
> restart C* and old data disapear, sometimes it needs to delete all C* data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
