ndra/configuration/configCassandra_yaml_r.html?scroll=reference_ds_qfg_n1r_1k__auto_snapshot
>>
>>
>>
>>
>>
>> *From:* Ali Akhtar [mailto:ali.rac...@gmail.com]
>> *Sent:* Sunday, April 26, 2015 10:31 PM
>>
>> *To:* user@cassandra.apache.org
>> *Subjec
...@gmail.com]
> *Sent:* Sunday, April 26, 2015 10:31 PM
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: Data model suggestions
>
>
>
> Thanks Peer. I like the approach you're suggesting.
>
>
>
> Why do you recommend truncating the last active table rat
/cassandra/configuration/configCassandra_yaml_r.html?scroll=reference_ds_qfg_n1r_1k__auto_snapshot
From: Ali Akhtar [mailto:ali.rac...@gmail.com]
Sent: Sunday, April 26, 2015 10:31 PM
To: user@cassandra.apache.org
Subject: Re: Data model suggestions
Thanks Peer. I like the approach you're sugge
Sharma [mailto:narendra.sha...@gmail.com]
> *Sent:* Friday, April 24, 2015 6:53 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Data model suggestions
>
>
>
> I think one table say record should be good. The primary key is record id.
> This will ensure good distribution.
> Just update
ting
> doesn’t create automatic snapshots.
>
>
>
>
>
> *From:* Narendra Sharma [mailto:narendra.sha...@gmail.com]
> *Sent:* Friday, April 24, 2015 6:53 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Data model suggestions
>
>
>
> I think one table say record
snapshots.
From: Narendra Sharma [mailto:narendra.sha...@gmail.com]
Sent: Friday, April 24, 2015 6:53 AM
To: user@cassandra.apache.org
Subject: Re: Data model suggestions
I think one table say record should be good. The primary key is record id. This
will ensure good distribution.
Just update
I think one table say record should be good. The primary key is record id.
This will ensure good distribution.
Just update the active attribute to true or false.
For range query on active vs archive records maintain 2 indexes or try
secondary index.
On Apr 23, 2015 1:32 PM, "Ali Akhtar" wrote:
>
Good point about the range selects. I think they can be made to work with
limits, though. Or, since the active records will never usually be > 500k,
the ids may just be cached in memory.
Most of the time, during reads, the queries will just consist of select *
where primaryKey = someValue . One ro
Hi,
If your external API returns active records, that means I am guessing you
need to do a select * on the active table to figure out which records in
the table are no longer active.
You might be aware that range selects based on partition key will timeout
in cassandra. They can however be made t
That's returned by the external API we're querying. We query them for
active records, if a previous active record isn't included in the results,
that means its time to archive that record.
On Thu, Apr 23, 2015 at 9:20 PM, Manoj Khangaonkar
wrote:
> Hi,
>
> How do you determine if the record is n
Hi,
How do you determine if the record is no longer active ? Is it a perioidic
process that goes through every record and checks when the last update
happened ?
regards
On Thu, Apr 23, 2015 at 8:09 AM, Ali Akhtar wrote:
> Hey all,
>
> We are working on moving a mysql based application to Cassa
11 matches
Mail list logo
