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:
> There are some issues work
There are some issues working on larger partitions.
Hbase doesn't do what you say! You have also to be carefull on hbase not to
create large rows! But since they are globally-sorted, you can easily sort
between them and create small rows.
In my opinion, cassandra people are wrong, in that they say
Well 1) I have not sent it to postgresql mailing lists 2) I thought this is
an open ended question as it can involve ideas from everywhere including
the Cassandra java driver mailing lists so sorry If that bothered you for
some reason.
On Wed, Oct 12, 2016 at 1:41 AM, Dorian Hoxha
wrote:
> Also,
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
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
