>querying them would be inefficient (impossible?
Impossible. In the case of multi-column partition key all of them must be
restricted in WHERE clause:
CREATE TABLE data.table (id1 int, id2 int, primary KEY ((id1,id2)));
SELECT * FROM data.table WHERE id1 = 0;
InvalidRequest: Error from server: co
No the employees would end up in arbitrary partitions, and querying them would
be inefficient (impossible? - I am levels back on C* so don’t know if ALLOW
FILTERING even works for this).
I would be tempted to use organization_id only or organization_Id and maybe a
few shard bits (if you are wor
In the case of PRIMARY KEY((organization_id, employee_id)), could I still
do a query like Select ... where organization_id = x, to get all employees
in a particular organization?
And, this will put all those employees in the same node, right?
On Sun, Oct 9, 2016 at 9:17 AM, Graham Sanderson wrot
Nomenclature is tricky, but PRIMARY KEY((organization_id, employee_id)) will
make organization_id, employee_id the partition key which equates roughly to
your latter sentence (I’m not sure about the 4 billion limit - that may be the
new actual limit, but probably not a good idea).
> On Oct 8, 2
the last '4 billion rows' should say '4 billion columns / cells'
On Sun, Oct 9, 2016 at 6:34 AM, Ali Akhtar wrote:
> Say I have the following primary key:
> PRIMARY KEY((organization_id, employee_id))
>
> Will this create 1 row whose primary key is the organization id, but it
> has a 4 billion c
Say I have the following primary key:
PRIMARY KEY((organization_id, employee_id))
Will this create 1 row whose primary key is the organization id, but it has
a 4 billion column / cell limit?
Or will this create 1 row for each employee in the same organization, so if
i have 5 employees, they will
