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 <jji...@gmail.com> wrote: > How many rows per partition in each model? > > > > On Jun 22, 2022, at 6:38 PM, MyWorld <timeplus.1...@gmail.com> 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 should we > maintain a seperate table for each or a single table. > > > > Model1 - Combined table > > Table(Pk,CK, col1,col2, col3, col4,col5) > > > > Model2 - Seperate tables > > Table1(Pk,CK,col1,col2,col3) > > Table2(Pk,CK,col3,col4,col45) > > > > So here partion and clustering keys are same. Also note column col3 is > required in both use cases. > > > > As per my thought in Model2, partition size would be less. There would > be less sstables and when I use level compaction, it could be easily > maintained. So should be better read performance. > > > > Please help me to highlight the drawback and advantage of each data > model. Here we have a mix kind of workload (read/write) >
