On 01/06/2016 04:47 PM, Robert Coli wrote:
On Wed, Jan 6, 2016 at 12:54 PM, Chris Burroughs
wrote:
The problem with that approach is that manually editing the local schema
tables in live cluster is wildly dangerous. I *think* this would work:
* Make triple sure no schema changes are happeni
On Wed, Jan 6, 2016 at 12:54 PM, Chris Burroughs
wrote:
> I work with Amir and further experimentation I can shed a little more
> light on what exactly is going on under the hood. For background our goal
> is to take data that is currently being read and written to via thrift,
> switch reads to
I work with Amir and further experimentation I can shed a little more light on
what exactly is going on under the hood. For background our goal is to take
data that is currently being read and written to via thrift, switch reads to
CQL, and then switch writes to CQL. This is in alternative to
On Tue, Dec 22, 2015 at 6:55 AM, Amir Hassani
wrote:
> Defining the “column_metadata” after table creation vs during table
> creation seems to affect the cql schema. We are running a large
> high-throughput Cassandra 2.1.10 cluster. During table creation, the client
> Cassandra-cli was used with
Hello,
Defining the “column_metadata” after table creation vs during table
creation seems to affect the cql schema. We are running a large
high-throughput Cassandra 2.1.10 cluster. During table creation, the client
Cassandra-cli was used with the following commands:
“create column family Test wi
