[
https://issues.apache.org/jira/browse/CASSANDRA-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-12916:
----------------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.x)
3.11
Reproduced In: 3.9, 3.8, 3.7, 3.6 (was: 3.6, 3.7, 3.8, 3.9)
Status: Resolved (was: Patch Available)
CI is clean, so I've committed to 3.11 in
{{9cc0c80de281e6c6f09187dd318deaa5b68cde82}} and merged to 3.X/trunk.
Thanks for the patch.
> 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.11
>
> 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)
