We did something similar with a split cloud/physical hardware deployment.
There was a weird requirement that app authentication data (fortunately in
it's own keyspace already) could not live on the cloud (shrug).
This ended up being a simple configuration change in the schema just like
your
Hi,
It seems like it should be possible to have a keyspace replicated only to a
subset of DC's on a given cluster spanning across multiple DCs? Is there
anything bad about this approach?
Scenario
Cluster spanning 4 DC's = CA, TX, NY, UT
Has multiple keyspaces such that
* keyspace_CA_TX -
It's often an excellent strategy. No known issues.
-Tupshin
On May 16, 2014 4:13 PM, Anand Somani meatfor...@gmail.com wrote:
Hi,
It seems like it should be possible to have a keyspace replicated only to
a subset of DC's on a given cluster spanning across multiple DCs? Is there
anything
