[jira] [Commented] (CASSANDRA-12916) Broken UDT muitations loading from CommitLog

["Tyler Hobbs (JIRA)" <ji...@apache.org>]

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

Tyler Hobbs commented on CASSANDRA-12916:
-----------------------------------------

The patch (with the Thrift followup fix) looks correct to me.

> Broken UDT muitations loading from CommitLog
> --------------------------------------------
>
>                 Key: CASSANDRA-12916
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12916
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>         Environment: Cassandra 3.9
>            Reporter: Sergey Dobrodey
>            Assignee: Sam Tunnicliffe
>            Priority: Critical
>              Labels: patch
>             Fix For: 3.x
>
>         Attachments: patch.diff, udt.cql
>
>
> UDT mutatitions seems to be broken. Simple example is attached. After steps from it, restart cassandra and during commit log reading it will fail with error:
> ERROR 09:34:46 Exiting due to error while processing commit log during initialization.
> org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation; saved to /tmp/mutation6087238241614604390dat.  This may be caused by replaying a mutation against a table with the same name but incompatible schema.  Exception follows: org.apache.cassandra.serializers.MarshalException: Not enough bytes to read 0th field data
> I resolved this problem, so my patch is in attachment.



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