title: Cassandra data model too many table
body: <p>I have a single structured row as input with write rate of 10K per seconds. Each row has 20 columns. Some queries should be answered on these inputs. Because most of the queries needs different <code>WHERE</code>, <code>GROUP BY</code> or <code>ORDER BY</code>, The final data model ended up like this:</p>
  
  <pre><code>primary key for table of query1 : ((column1,column2),column3,column4)
  primary key for table of query2 : ((column3,column4),column2,column1)
    and so on
  </code></pre>
  
  <p>I am aware of the limit in number of tables in Cassandra data model (200 is warning and 500 would fail)</p>
  
  <p>Because for every input row I should do an insert in every table, the final write per seconds became big * big data!:</p>
  
  <pre><code>writes per seconds = 10K (input)
                          * number of tables (queries)
                          * replication factor
  </code></pre>
  
  <p>The main question: am I on the right path? Is it normal to have a table for every query even when the input rate is already so high?</p>
  
  <p>Shouldn't I use something like spark or hadoop instead of relying on bare datamodel? Or event Hbase instead of Cassandra?</p>