r/14bs9zvasf/cassandra-schema-migrator
>
> On Thu, Jan 29, 2015 at 9:16 AM, José Guilherme Vanz <
> guilherme@gmail.com> wrote:
>
>> Hi, Ricardo
>>
>> Thank you for your quick reply. =]
>> I'll take a look in the mutagen-cassandra and others I find in
thub.com/fromanator/mutagen-cassandra
>
> You may find other options in the mail list archives.
>
> Cheers,
>
> On Thu, Jan 29, 2015 at 8:31 AM, José Guilherme Vanz <
> guilherme@gmail.com> wrote:
>
>> Hello
>>
>> I am studying Cassandra for while and
Hello
I am studying Cassandra for while and to practice the libraries and
concepts I will implement a simple Cassandra client. During my research I
faced a doubt about schema migrations. What the common/best practice in
production clusters? I mean, who actually make the schema migration? The
appli
Hi, everyone
I have a development machine running in the UTC -0200
But the Cassandra in the same machine looks like is not running in the same
UTC because the logs are 2 hours ahead ( UTC ). For example, if my machine
is 08:49 and the Cassandra log entries are 10:49. And I'm trying change the
time
text,
>PRIMARY KEY((date_bucket),log_timestamp) // you may add server_id or
> log_type as clustering column optionally
> );
>
> For this table, the date_bucket should be chosen very carefully because
> for the same bucket, we're going to store logs of ALL servers and all t
n key? And if I want to query all logs in a period
of time how can I select I range o rows? Do I have to duplicate date column
( considering I have to use = operator with partition key ) ?
All the best
--
Att. José Guilherme Vanz
br.linkedin.com/pub/josé-guilherme-vanz/51/b27/58b/
