e misses a schema
> > update, it will figure this out when it notices that it’s local schema
> > version is behind the one being gossiped by the rest of the cluster, and
> > will pull the updated schema from the other nodes in the cluster.
> >
> >
> >
> >
hema
> version is behind the one being gossiped by the rest of the cluster, and
> will pull the updated schema from the other nodes in the cluster.
>
>
>
> From: Rahul Singh
> Reply-To:
> Date: Tuesday, April 17, 2018 at 4:13 PM
> To:
> Subject: Re: where d
when it notices that it’s local schema version is behind
the one being gossiped by the rest of the cluster, and will pull the updated
schema from the other nodes in the cluster.
From: Rahul Singh
Reply-To:
Date: Tuesday, April 17, 2018 at 4:13 PM
To:
Subject: Re: where does c* store the
It uses a “everywhere” replication strategy and its recommended to do all alter
/ create / drop statements with consistency level all — meaning it wouldn’t
make the change to the schema if the nodes are up.
--
Rahul Singh
rahul.si...@anant.us
Anant Corporation
On Apr 17, 2018, 12:31 AM -0500,
Yes, I know it must be in system schema.
But how c* replicates the user defined schema to all nodes? If it
applies the same RWN model to them, then what's the R and W?
And when a failed node comes back to the cluster, how to recover the
schema updates it may miss during the outage?
2018-04-16 17:
There is a system_schema keyspace to store all the schema information
https://docs.datastax.com/en/cql/3.3/cql/cql_using/useQuerySystem.html#useQuerySystem__table_bhg_1bw_4v
On Mon, Apr 16, 2018 at 10:48 AM, Jinhua Luo wrote:
> Hi All,
>
> Does c* use predefined keyspace/tables to store the use
Hi All,
Does c* use predefined keyspace/tables to store the user defined schema?
If so, what's the RWN of those meta schema? And what's the procedure
to update them?
-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
