Well you lose the atomicity and isolation, but in this case that is probably
fine
That said, in every interaction I’ve had with static columns, they seem to be
an odd duck (e.g. adding or complicating range slices), perhaps worthy of their
own code path and sstables. Just food for thought.
> O
If you want it in a separate sstable, just use a separate table. There's
nothing that warrants making the codebase more complex to accomplish
something it already does.
On Thu, Apr 30, 2015 at 5:07 PM graham sanderson wrote:
> Anyone here have an opinion; how realistic would it be to have a sep
How would it be different from creating an actual real extra table instead?
--
AY
On May 1, 2015 at 03:07:01, graham sanderson (gra...@vast.com) wrote:
Anyone here have an opinion; how realistic would it be to have a separate
memtable/sstable for static columns?
Begin forwarded message:
From
Anyone here have an opinion; how realistic would it be to have a separate
memtable/sstable for static columns?
> Begin forwarded message:
>
> From: Jonathan Haddad
> Subject: Re: DateTieredCompactionStrategy and static columns
> Date: April 30, 2015 at 3:55:46 PM CDT
> To: u...@cassandra.apache
