Hi there,
Please don't be worried about under utilization of CPU/RAM as it will
increase with active usage of the data in due course.
However, as pointed out already by other members , you may want to relook
at the hardware itself wherein 5TB per node storage with higher CPU+RAM can
rather be
I will recommend against this idea. And here is why (at a higher level of
abstraction)
1. This means the cloud services aren't reliable in the first place. That
itself is a big problem. Else with reliability guarantees and
multi-region/zone it should be pretty safe to stay in one place.
2. Devil
Hi Asad,
Seems to me that your development team will need to remodel the tables
sooner than later. This problem can't be left unattended for long once it
starts hitting severely.
The way Cassandra is, you may want to have them replicate the same table
with different PK / structure to suitably
Hi 'Users' :),
Just wanted to seek your opinion on the approach, should you please spare
some time on it.
https://www.slideshare.net/devopam/cassandra-table-modeling-an-alternate-approach
regards
Dev
Env:
[cqlsh 5.0.1 | Cassandra 3.11.2 | CQL spec 3.4.4 | Native protocol v4]
I am trying to ingest a csv that has date in MM/DD/ format ( %m/%d/%Y
).
While trying to load I am providing the WITH datetimeformat = '%m/%d/%Y'
but still getting errored out *time data '03/12/2019' does not match
hi ,
Just wondering if it would make sense to have support for timestamp
datatype in CQL native aggregates like MAX/MIN.
--
Devopam Mittra
Life and Relations are not binary
