[
https://issues.apache.org/jira/browse/CASSANDRA-12351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403811#comment-15403811
]
mck edited comment on CASSANDRA-12351 at 8/2/16 11:38 AM:
----------------------------------------------------------
{quote}If the code is /sensitive/ in this way maybe adding some assert
statements into CFS would be a good idea, like
assert cf == null || cf.hasColumns() || cf.isMarkedForDelete(){quote}
I take that back. The code is all over the place. It's a shame that CF can have
multiple states representing the same thing.
I can apply the patch, along with a unit test. But a number of tests in
ColumnFamilyStoreTest needs adjustment.
I can apply a different patch, one that improves
{{isEmptySchemaPartition(partition)}}.
Or you [~slebresne] can revert CASSANDRA-11427.
was (Author: michaelsembwever):
{quote}If the code is /sensitive/ in this way maybe adding some assert
statements into CFS would be a good idea, like
assert cf == null || cf.hasColumns() || cf.isMarkedForDelete(){quote}
I take that back. This code is all over the place. It's a shame that CF can
have multiple states representing the same thing.
I can apply the patch, along with a unit test. But a number of tests in
ColumnFamilyStoreTest needs adjustment.
I can apply a different patch, one that improves
{{isEmptySchemaPartition(partition)}}.
Or you [~slebresne] can revert CASSANDRA-11427.
> IllegalStateException: empty rows returned when reading
> system.schema_keyspaces
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-12351
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12351
> Project: Cassandra
> Issue Type: Bug
> Components: Local Write-Read Paths
> Reporter: mck
> Assignee: mck
>
> After 2.2.6 the following error is thrown during startup, resulting in
> Cassandra not starting.
> {noformat}
> CassandraDaemon.java:644 - Exception encountered during startup
> java.lang.IllegalStateException: One row required, 0 found
> at
> org.apache.cassandra.cql3.UntypedResultSet$FromResultSet.one(UntypedResultSet.java:77)
> ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at
> org.apache.cassandra.schema.LegacySchemaTables.createKeyspaceFromSchemaPartition(LegacySchemaTables.java:758)
> ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at
> org.apache.cassandra.schema.LegacySchemaTables.createKeyspaceFromSchemaPartitions(LegacySchemaTables.java:737)
> ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at
> org.apache.cassandra.schema.LegacySchemaTables.readSchemaFromSystemTables(LegacySchemaTables.java:219)
> ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at org.apache.cassandra.config.Schema.loadFromDisk(Schema.java:117)
> ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at org.apache.cassandra.config.Schema.loadFromDisk(Schema.java:107)
> ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:215)
> [apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:522)
> [apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:631)
> [apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> {noformat}
> In {{LegacySchemaTables.readSchemaFromSystemTables(..)}} the call to
> {{getSchemaPartitionsForTable(KEYSPACES)}} is now (since 2.2.6) returning
> more rows. The additional rows are empty.
> These rows are coming out of the row iterator post 2.2.6, where they were not
> in 2.2.6.
> This issue was raised on the mailing list
> [here|http://mail-archives.apache.org/mod_mbox/cassandra-user/201607.mbox/%[email protected]%3E].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
