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

Philip Thompson edited comment on CASSANDRA-9148 at 4/9/15 2:57 PM:
--------------------------------------------------------------------

What Cassandra version were you using? Can you paste the full schemas of the 
types and tables you were using?

How did you try to alter the type schema? What exact insert query threw the 
InvalidQueryException?


was (Author: philipthompson):
What Cassandra version were you using? Can you paste the full schemas of the 
types and tables you were using?

> Issue when modifying UDT
> ------------------------
>
>                 Key: CASSANDRA-9148
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9148
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Oskar Kjellin
>             Fix For: 2.1.5
>
>
> I'm trying out the user defined types but ran into some issues when adding a 
> column to an existing type.
> Unfortunately I had to scrap the entire cluster so I cannot access it any 
> more.
> After creating the UDT i adde two tables using it. 1 was just using 
> frozen<type>. The other was using both frozen<type> frozen map<String, type>.
> Then I realized I needed to add a new field to the user type. Then when I 
> tried to put to any of the two tables (setting all fields to the UDT in the 
> datastax java driver) I got this error message that I could not find anywhere 
> else but in the cassandra code:
> com.datastax.driver.core.exceptions.InvalidQueryException: Invalid remaining 
> data after end of UDT value
> I had to scrap my keyspace in order to be able to use it again. Could not 
> even drop one of the tables.
> I know that they are frozen so we cannot modify the value of individual 
> fields once they are written but we must be able to modify the schema right?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to