Hi
For us, clearly the willing to improve (and not give up) materialized views
with a quality testing follow up
https://issues.apache.org/jira/browse/CASSANDRA-15921
Materialized view is a fantastic tool very useful for us.
Our use case is to deduplicate and order : We want to store the last
Hi all,
Following a discussion with our adminsys, I have a very practical question.
We use cassandra proxies (-Dcassandra.join_ring=false) as coordinators for PHP
clients (a loot of PHP clients).
Our problem is that restarting Cassandra on proxies sometimes fails with the
following error :
or a fastcgi pool?
Are the coordinators/proxies here just to handle a ridiculous number of
clients, or is it the cost of connecting that's hurting as you blow up the
native thread pool on connect for expensive auth?
On Wed, Mar 17, 2021 at 5:44 AM Regis Le Bretonnic
mailto:r.lebreton...@meetic-corp.
Clear… Thanks for the detailed answer…
De : Jeff Jirsa
So, 30s or -Dcassandra.ring_delay_ms= on the command line, but note that this
ALSO impacts normal startup/shutdown/expand/shrink/etc type operations, and if
you have to ask how to change it, you probably shouldn't.
- Jeff
Probably DLLs that are not registered.
You should cleanly install Cassandra and java... and then copy your keyspaces
(...\cassandra\data contents)
Hi (also posted in dev mailing list but not sure I can publish on it),
We use datastax cassandra java driver v4.15.0 and we want to limit
connexion only to Cassandra proxy nodes (Nodes with no data started
with option: -Dcassandra.join_ring=false).
For that:
- we configured the driver to have
We have tested Stargate and were very disappointed...
Originally our architecture was PHP microservices (with FPM) + cassandra
proxies.
But we were blocked because PHP driver is no more supported.
We made tests to keep PHP + stargate but there were many issues, the main
one (but not the only
tests with java, we still have our 80 proxy nodes.
We have defined 4 of them as contact point, also being in a whitelist
policy.
Le ven. 13 oct. 2023 à 01:27, Regis Le Bretonnic <
r.lebreton...@meetic-corp.com> a écrit :
> Hi Stefan,
>
> Your analysis is exactly what happen !
&
Hi Stefan,
Your analysis is exactly what happen !
What I can say is that we are migrating from php to java and the behaviour
of the php (or cpp) driver is completely different.
* The topology of the cassandra cluster returned by the contact point with
the php driver includes data nodes + proxy
e user_id = Joe;
>
> So I get Karen and Julia
>
> And then for each such visitor I do
>
> select visit_date from visits where user_id = Joe and visitor_id = Julia
> limit 1
>
>
> From: Regis Le Bretonnic
> Sent: Tuesday, August
10;
>
> Use TTL of e.g. 1 month? So rows would start to disappear automatically.
> If somebody visited me 2 months ago and then it disappears next I would not
> care at all. A user who visited me 2 months ago is basically equal to a
> user who has never visited me.
>
>
> _
t; Hi surbhi ,
> There are 2 drawbacks associated with MV.
> 1. Inconsistent view
> 2. The lock it takes on the base table. This gets worse when you have huge
> number of clustering keys in a specific partition.
>
> It's better you re-design a seperate table and let your API do a p
Hi...
We do the same (even if a lot of people will say it's bad and that you
shouldn't...) with a "allow filtering" BUT ALWAYS WITHIN A PARTITION AND
WITH A LIMIT CLAUSE TO AVOID A FULL PARTITION SCAN.
.
So you need to know the organisation_id and the product_type...
and paginate your result
Hi Surbhi
We do use cassandra materialized views even if not recommended.
There are known issues you have to make with. Despite of them, we still use
VM.
What we observe is :
* there are inconsistency issues but few. Most of them are rows that
should not exist in the MV...
* we made a spark
14 matches
Mail list logo
