From 8e259f3c7d6003d368e0bac2155f2bc2fe7a5c99 Mon Sep 17 00:00:00 2001 From: Cameron Zemek Date: Fri, 23 Oct 2020 11:41:41 +1000 Subject: [PATCH] LegacyLayout does not have same behavior as 2.x when handling unknown column names (CASSANDRA-15081) --- src/java/org/apache/cassandra/db/LegacyLayout.java | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/java/org/apache/cassandra/db/LegacyLayout.java b/src/java/org/apache/cassandra/db/LegacyLayout.java index bb652a76d704..1835ed5635da 100644 --- a/src/java/org/apache/cassandra/db/LegacyLayout.java +++ b/src/java/org/apache/cassandra/db/LegacyLayout.java @@ -1179,10 +1179,10 @@ public static LegacyAtom readLegacyAtom(CFMetaData metadata, DataInputPlus in, b // but we don't do this here and re-throw the exception because the calling code sometimes has to know // about this happening. This does mean code calling this method should handle this case properly. if (!metadata.ksName.equals(SchemaConstants.SYSTEM_KEYSPACE_NAME) && metadata.getDroppedColumnDefinition(e.columnName) == null) - throw new IllegalStateException(String.format("Got cell for unknown column %s in sstable of %s.%s: " + - "This suggest a problem with the schema which doesn't list " + - "this column. Even if that column was dropped, it should have " + - "been listed as such", metadata.ksName, metadata.cfName, UTF8Type.instance.compose(e.columnName)), e); + logger.warn(String.format("Got cell for unknown column %s in sstable of %s.%s: " + + "This suggest a problem with the schema which doesn't list " + + "this column. Even if that column was dropped, it should have " + + "been listed as such", metadata.ksName, metadata.cfName, UTF8Type.instance.compose(e.columnName)), e); throw e; }