Why does Cassandra need to have 2B column limit? why can't we have unlimited ?

Hi All, I understand Cassandra can have a maximum of 2B rows per partition but in practice some people seem to suggest the magic number is 100K. why not create another partition/rowkey automatically (whenever we reach a safe limit that we consider would be efficient) with auto increment bigint

Re: Why does Cassandra need to have 2B column limit? why can't we have unlimited ?

I did mention this in my previous email. This is not time series data. I understand how to structure it if it is a time series data/ What do you mean globally sorted? you mean keeping every partition sorted (since I come from Casandra world)? rowkey 1 -> blob page -> int or long or bigint col1

Re: Why does Cassandra need to have 2B column limit? why can't we have unlimited ?

Also, I'm not sure, but I don't think it's "cool" to write to multiple lists in the same message. (based on postgresql mailing lists rules). Example I'm not subscribed to those, and now the messages are separated. On Wed, Oct 12, 2016 at 10:37 AM, Dorian Hoxha wrote: >