Re: [EXTERNAL] Re: Running select against cassandra

2020-02-06 Thread Reid Pinchback
? and minute = ? Sean Durity From: Reid Pinchback Sent: Thursday, February 6, 2020 4:10 PM To: user@cassandra.apache.org Subject: Re: [EXTERNAL] Re: Running select against cassandra Abdul, When in doubt, have a query model that immediately feeds you exactly what you are looking for. That’s kin

RE: [EXTERNAL] Re: Running select against cassandra

2020-02-06 Thread Durity, Sean R
:10 PM To: user@cassandra.apache.org Subject: Re: [EXTERNAL] Re: Running select against cassandra Abdul, When in doubt, have a query model that immediately feeds you exactly what you are looking for. That’s kind of the data model philosophy that you want to shoot for as much as feasible with C

RE: [EXTERNAL] Re: Running select against cassandra

2020-02-06 Thread Durity, Sean R
From reports on this mailing list, I do not allow materialized views. Sean Durity From: Reid Pinchback Sent: Thursday, February 6, 2020 4:10 PM To: user@cassandra.apache.org Subject: Re: [EXTERNAL] Re: Running select against cassandra Abdul, When in doubt, have a query model that immediately

Re: [EXTERNAL] Re: Running select against cassandra

2020-02-06 Thread Reid Pinchback
. You might want a composite partition key for having an efficient selection of narrow time ranges. From: Abdul Patel Reply-To: "user@cassandra.apache.org" Date: Thursday, February 6, 2020 at 2:42 PM To: "user@cassandra.apache.org" Subject: Re: [EXTERNAL] Re: Running sele

Re: [EXTERNAL] Re: Running select against cassandra

2020-02-06 Thread Abdul Patel
this is the schema similar to what we have , they want to get user connected - concurrent count for every say 1-5 minutes. i am thinking will simple select will have performance issue or we can go for materialized views ? CREATE TABLE usr_session ( userid bigint, session_usr text,

RE: [EXTERNAL] Re: Running select against cassandra

2020-02-06 Thread Durity, Sean R
Do you only need the current count or do you want to keep the historical counts also? By active users, does that mean some kind of user that the application tracks (as opposed to the Cassandra user connected to the cluster)? I would consider a table like this for tracking active users through