For the example provided by you , are you saying you are getting two rows
for same pk1,pk2,time?
It may be a problem with your inserts when you are inserting multiple
distinct rows or to validate all nodes are in sync try fetching using
CONSISTENCY ALL in cql.
On 18-Aug-2017 9:37 PM, "Nathan McL
@Sagar,
A query to get the data looks like this (primary key values included in the
query).
SELECT * FROM table WHERE pk1='2269202-onstreet_high' AND pk2=2017 AND
time='2017-07-18 03:15:00+';
(in actual practice, the queries in our code would use query a range of
time values).
@Cristophe
I
What is your query to fetch rows. Can you share P1,pk2,time for the sample
rows you pasted?
On 17-Aug-2017 2:20 AM, "Nathan McLean" wrote:
> Hello All,
>
> I have a Cassandra cluster with a table similar to the following:
>
> ```
> CREATE TABLE table (
> pk1 text,
> pk2 int,
> time t
Hi Nathan,
The code may occasionally write to the same row multiple times.
>
>
Can you run a test using IF NOT EXISTS in your inserts to see if that makes
a difference? That shouldn't make a difference, but I don't see what the
problem might be at the moment.
--
*Christophe Schmitz**Director
Hello All,
I have a Cassandra cluster with a table similar to the following:
```
CREATE TABLE table (
pk1 text,
pk2 int,
time timestamp,
...
probability list,
PRIMARY KEY ((pk1, pk2), time)
) WITH CLUSTERING ORDER BY (time DESC)
```
Python processes write to this table us
