[ 
https://issues.apache.org/jira/browse/CASSANDRA-9148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeff Jirsa updated CASSANDRA-9148:
----------------------------------
    Attachment: 9148-2.1.txt

Apologies for [~blerer], didn't notice he was already assigned. Perhaps he can 
review. 

Adding patch. Should apply to both 2.1 and trunk. Also on github against trunk: 
https://github.com/jeffjirsa/cassandra/commit/2853aa4e01dd91f15b47a829bb53c499c729c5d8.diff

Or against 2.1 (identical): 
https://github.com/jeffjirsa/cassandra/commit/3375ac6fc1dc15f414e8d594f854dee2676711fd.diff

Includes unit test. 

The assert in db/composites/CellNames.java is to throw an AssertionError rather 
than an NPE if there's another code path that somehow hits this same issue. 


> 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
>            Assignee: Benjamin Lerer
>             Fix For: 2.1.5
>
>         Attachments: 9148-2.1.txt
>
>
> 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