Hey Joseph,
Also, in your materialized view I think the “clustering order by” should have
started with policy_id, so it would have been: …WITH CLUSTERING ORDER
BY(policy_id, device_id, date_created DESC);
however that doesn’t seem very performant.
Maybe in the materialized view the pr
Joseph,
In this statement from your email:
SELECT * FROM m_ps_project_policy_device4 where project_id=1337 and
policy_id=7331 and device_id='1234567890' group by policy_id, device_id limit 1;
…why would you have the “group by policy_id, device_id” section at all when you
are already doin
Hi all,
I am bumping this email hoping that it can reach a larger audience.
Thanks,
Joseph
On Tue, Feb 12, 2019 at 11:45 AM Joseph Wonesh
wrote:
> Hello,
>
> I have a materialized view defined by the following:
>
> CREATE MATERIALIZED VIEW m_ps_project_policy_device0 AS
>SELECT policy_
We have small table records are about 5k .
All the inserts comes as 4hr ttl and we have table level ttl 1 day and gc
grace seconds has 3 hours. We do 5k reads a second during peak load.
During the peak load seeing Alerts for tomstone scanned histogram reaching
million.
Cassandra version 3.11.1. Pl
Hello Cassandra users!
At Ericsson we open sourced some of the Cassandra tools that we have developed
and used internally.
Feel free to try them out and see what you think about them, any feedback is
appriciated.
ecAudit - Audit plugin
https://github.com/ericsson/ecaudit
For those looking to g
