I need to get all unique keys (not the complete primary key, just the
partition key) in order to aggregate all the relevant records of that key
and apply some calculations on it.
*CREATE TABLE my_table (
id text,
timestamp bigint,
value double,
PRIMARY KEY (id, timestamp) )*
I
You'd use different num_tokens only if you wanted an imbalance (e.g. New
hardware specs where you wanted to use fewer, larger machines).
--
Jeff Jirsa
> On Aug 19, 2017, at 6:04 PM, Subroto Barua
> wrote:
>
> Jeff,
>
> is it ok to have different values of num_tokens per node in a cluster?
Jeff,
is it ok to have different values of num_tokens per node in a cluster? won't it
create cluster imbalance? or it better to initiate it on a separate DC?
Subroto
On Friday, August 18, 2017, 5:34:11 AM PDT, Durity, Sean R
wrote:
#yiv5432100827 #yiv5432100827 -- _filtered #yiv5432100827 {pan
That's the only way to get this done then, break writes and fix them with
incremental repairs?
On Friday, August 18, 2017, 5:17:38 PM PDT, kurt greaves
wrote:
You need to run an incremental repair for sstables to be marked repaired.
However only if all of the data in that Sstable is repaired
