cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-12916) Broken UDT muitations loading from CommitLog
Date Fri, 18 Nov 2016 17:16:59 GMT


Sam Tunnicliffe updated CASSANDRA-12916:
    Fix Version/s: 3.x
    Reproduced In: 3.9, 3.8, 3.7, 3.6  (was: 3.6, 3.7, 3.8, 3.9)
           Status: Patch Available  (was: Open)

Looks like this problem has been around since non-frozen UDTs were introduced.
I've re-written the patch slightly and added some unit tests, [~thobbs] as the author of CASSANDRA-7423,
would you mind casting your eye over it please?
The 3.X patch merges cleanly to trunk.


> Broken UDT muitations loading from CommitLog
> --------------------------------------------
>                 Key: CASSANDRA-12916
>                 URL:
>             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
> I resolved this problem, so my patch is in attachment.

This message was sent by Atlassian JIRA

View raw message