Hi,
I believe the "tDate" is stored with milliseconds precision which could explain
why these duplicate dates are shown.
Could you try running the following query:
"SELECT userid, secondaryid, blobAsBigint(timestampAsBlob("tDate")), tid3,
sid4, pid5, associate_degree FROM user_data;"
The "tDat
can you run this:
select associate_degree, writetime( associate_degree ) from user_data where
Thanks,
James
On Wed, Aug 22, 2018 at 7:13 PM, James Shaw wrote:
> can you run this:
> select writetime( associate_degree ) from user_data where
> see what are writetime
>
> On Wed, Aug 22,
can you run this:
select writetime( associate_degree ) from user_data where
see what are writetime
On Wed, Aug 22, 2018 at 7:03 PM, James Shaw wrote:
> interesting. what are insert statement and select statement ?
>
> Thanks,
>
> James
>
> On Wed, Aug 22, 2018 at 6:55 PM, Gosar M
> wrote:
interesting. what are insert statement and select statement ?
Thanks,
James
On Wed, Aug 22, 2018 at 6:55 PM, Gosar M
wrote:
> CREATE TABLE user_data (
> "userid" text,
> "secondaryid" text,
> "tDate" timestamp,
> "tid3" text,
> "sid4" text,
> "pid5" text,
> associat
CREATE TABLE user_data (
"userid" text,
"secondaryid" text,
"tDate" timestamp,
"tid3" text,
"sid4" text,
"pid5" text,
associate_degree text
PRIMARY KEY (("userid", "secondaryid"),"tDate", "tid3", "sid4", "pid5")
WITH CLUSTERING ORDER BY ("tDate" ASC, "tid3" ASC, "si
What is the schema of the table? Could your include the output of DESCRIBE?
Dinesh
On Wednesday, August 22, 2018, 2:22:31 PM PDT, Gosar M
wrote:
Hello,
Have a table with following partition and clustering keys
partition key - ("userid", "secondaryid"),
clustering key - "tDate", "tid3"
Hello,
Have a table with following partition and clustering keys
partition key - ("userid", "secondaryid"),
clustering key - "tDate", "tid3", "sid4", "pid5"
Data is inserted based on above partition and clustering key. For 1 record
seeing 2 rows returned when queried by both partition and cluster
