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 <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) >
