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

Robert Stupp reopened CASSANDRA-14749:
--------------------------------------

Seems that this commit broke the build:
{code:java}
build-test:
[javac] Compiling 540 source files to 
/home/automaton/cassandra-src/build/test/classes
[javac] 
/home/automaton/cassandra-src/test/unit/org/apache/cassandra/db/LegacyLayoutTest.java:279:
 error: Clustering is abstract; cannot be instantiated
[javac] builder.newRow(new Clustering(UTF8Serializer.instance.serialize("a")));
[javac] ^
[javac] 
/home/automaton/cassandra-src/test/unit/org/apache/cassandra/db/LegacyLayoutTest.java:280:
 error: no suitable method found for 
live(CFMetaData,ColumnDefinition,long,ByteBuffer,<null>)
[javac] builder.addCell(BufferCell.live(table, v, 0L, 
Int32Serializer.instance.serialize(1), null));
[javac] ^
[javac] method BufferCell.live(ColumnDefinition,long,ByteBuffer) is not 
applicable
[javac] (actual and formal argument lists differ in length)
[javac] method BufferCell.live(ColumnDefinition,long,ByteBuffer,CellPath) is 
not applicable
[javac] (actual and formal argument lists differ in length)
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 2 errors
{code}

> Collection Deletions for Dropped Columns in 2.1/3.0 mixed-mode can delete rows
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14749
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14749
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Major
>             Fix For: 3.0.18
>
>
> Similar to CASSANDRA-14568, if a 2.1 node sends a response to a 3.0 node 
> containing a deletion for a dropped collection column, instead of deleting 
> the collection, we will delete the row containing the collection.
>  
> This is an admittedly unlikely cluster state but, during such a state, a 
> great deal of data loss could happen.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to