other tech for
> any other reason that seeing it as a better fit)
>
> On Fri, Mar 25, 2016 at 1:31 PM, K. Lawson wrote:
>
>> While adhering to best practices, I am trying to model a time series in
>> Cassandra that is compliant with the following access pattern directives:
the cluster.
>
> The big problem is that rapid, large-scale removal from the queue
> generates tons of tombstones that need to be removed.
>
> The DateTieredCompactionStrategy may help as well.
>
> -- Jack Krupansky
>
> On Fri, Mar 25, 2016 at 8:31 AM, K. Lawson wrote:
Sean, the link you have supplied does not seem to work.
On Fri, Mar 25, 2016 at 9:43 AM, wrote:
> You might take a look at this previous conversation on queue-type
> applications and Cassandra. Generally this is an anti-pattern for a
> distributed system like Cassandra.
>
>
> https://mail-archiv
While adhering to best practices, I am trying to model a time series in
Cassandra that is compliant with the following access pattern directives:
- Is to be both read and shrank by a single party, grown by multiple parties
- Is to be read as a queue (in other words, its entries, from first to
last
I want to create a table with wide partitions (or, put another way, a table
which has no value columns (non primary key columns)) that enables the
number of rows in any of its partitions to be efficiently procured. Here is
a simple definition of such a table
CREATE TABLE IF NOT EXISTS test_table
