You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Podkowinski (JIRA)" <ji...@apache.org> on 2015/08/06 11:39:05 UTC

[jira] [Commented] (CASSANDRA-9960) UDTs still visible after drop/recreate keyspace

    [ https://issues.apache.org/jira/browse/CASSANDRA-9960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659749#comment-14659749 ] 

Stefan Podkowinski commented on CASSANDRA-9960:
-----------------------------------------------

There's a known issue with cqlsh caching UDT definitions (CASSANDRA-9188). I'm not sure if I understand your description correctly, but could this be the issue here as well?

> 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)