Thanks a lot Jeff, Michiel and Manish for your replies. Really helpful.
On Thu, Jun 23, 2022, 9:50 AM Jeff Jirsa wrote:
> This is assuming each row is like … I dunno 10-1000 bytes. If you’re
> storing like a huge 1mb blob use two tables for sure.
>
> On Jun 22, 2022, at 9:06 PM, Jeff Jirsa
This is assuming each row is like … I dunno 10-1000 bytes. If you’re storing
like a huge 1mb blob use two tables for sure.
> On Jun 22, 2022, at 9:06 PM, Jeff Jirsa wrote:
>
>
>
> Ok so here’s how I would think about this
>
> The writes don’t matter. (There’s a tiny tiny bit of nuance in
Ok so here’s how I would think about this
The writes don’t matter. (There’s a tiny tiny bit of nuance in one table where
you can contend adding to the memtable but the best cassandra engineers on
earth probably won’t notice that unless you have really super hot partitions,
so ignore the
Hi Jeff,
Let me know how no of rows have an impact here.
May be today I have 80-100 rows per partition. But what if I started
storing 2-4k rows per partition. However total partition size is still
under 100 MB
On Thu, Jun 23, 2022, 7:18 AM Jeff Jirsa wrote:
> How many rows per partition in each
I guess it will depend on your use case.
If your columns for table1 and table2 are significant in size it might be the
case that model 2 is faster and you could perform queries in parallel, but …
If you always need to retrieve both the row from table1 and table2, then both
queries together might
Table1 should be fine if some column values are not entered than Cassandra
will not create entry for them so partiton will almost be same in
both cases.
On Thu, Jun 23, 2022, 07:08 MyWorld wrote:
> Hi all,
>
> Just a small query around data Modelling.
> Suppose we have to design the data model
How many rows per partition in each model?
> On Jun 22, 2022, at 6:38 PM, MyWorld wrote:
>
>
> Hi all,
>
> Just a small query around data Modelling.
> Suppose we have to design the data model for 2 different use cases which will
> query the data on same set of (partion+clustering key). So
Hi all,
Just a small query around data Modelling.
Suppose we have to design the data model for 2 different use cases which
will query the data on same set of (partion+clustering key). So should we
maintain a seperate table for each or a single table.
Model1 - Combined table
Table(Pk,CK,
Nothing to see here...because well, it's a podcast, right? But I did get to
spend some time with Patrick McFadin discussing our favorite database -
Apache Cassandra! Listen in as we talk a little about the early days of
Cassandra as well as the new, upcoming Cassandra 4.1 release.
