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

Yazal Ulloa updated CASSANDRA-16320:
------------------------------------
    Description: 
I'm using Cassandra 3.11.6 on Centos 7 with a 3 node cluster, I ran some schema 
changes, drop tables/materialized views, alter tables, etc, after that one of 
the materialized views was failing with this error: 
 org.apache.cassandra.schema.SchemaKeyspace$MissingColumns: No partition key 
columns found in schema table for my_keyspace.my_materialized_view.

 

I ran nodetool describecluster and found the schema version was different, I 
tried to run a repair, it didn't work, I restarted the nodes, but they didn't 
start.

  was:
I'm using Cassandra 3.11.6 on Centos 7 with a 3 node cluster, I ran some schema 
changes, drop tables/materialized views, alter tables, etc, after that one of 
the materialized views was failing with this error: 
org.apache.cassandra.schema.SchemaKeyspace$MissingColumns: No partition key 
columns found in schema table for my_keyspace.my_materialized_view.


> Cassandra fails to start after schema changed
> ---------------------------------------------
>
>                 Key: CASSANDRA-16320
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16320
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Yazal Ulloa
>            Priority: Normal
>
> I'm using Cassandra 3.11.6 on Centos 7 with a 3 node cluster, I ran some 
> schema changes, drop tables/materialized views, alter tables, etc, after that 
> one of the materialized views was failing with this error: 
>  org.apache.cassandra.schema.SchemaKeyspace$MissingColumns: No partition key 
> columns found in schema table for my_keyspace.my_materialized_view.
>  
> I ran nodetool describecluster and found the schema version was different, I 
> tried to run a repair, it didn't work, I restarted the nodes, but they didn't 
> start.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to