On 2017-07-20 08:17 (-0700), Nitan Kainth <ni...@bamlabs.com> wrote:
> Jeff,
>
> It is really strange, look at below log, I inserted your data and then few
> additional; finally, the issue is reproduced:
>
..
> (6 rows)
> cqlsh> insert into test.t(a) values('b');
> cqlsh> select a,b, writetime (b) from test.t;
>
> a | b | writetime(b)
> ---+------+------------------
> z | null | null
> a | null | null
> e | null | null
> r | null | null
> w | null | null
> t | x | 1500563698113119
> b | null | 1500563698113119
>
> (7 rows)
>
Repro'd on my side too.
cqlsh> insert into test.t(a,b) values('t','x');
cqlsh> insert into test.t(a) values('b');
cqlsh> select a,b, writetime (b) from test.t;
a | b | writetime(b)
---+------+------------------
z | null | null
e | null | null
r | null | null
w | null | null
t | x | 1500565131354883
b | null | 1500565131354883
Here's what the data on disk looks like (starting with row 'w'):
{
"partition" : {
"key" : [ "w" ],
"position" : 69
},
"rows" : [
{
"type" : "row",
"position" : 92,
"liveness_info" : { "tstamp" : "2017-07-20T04:41:59.005382Z" },
"cells" : [ ]
}
]
},
{
"partition" : {
"key" : [ "t" ],
"position" : 93
},
"rows" : [
{
"type" : "row",
"position" : 120,
"liveness_info" : { "tstamp" : "2017-07-20T15:38:51.354883Z" },
"cells" : [
{ "name" : "b", "value" : "x" }
]
}
]
},
{
"partition" : {
"key" : [ "b" ],
"position" : 121
},
"rows" : [
{
"type" : "row",
"position" : 146,
"liveness_info" : { "tstamp" : "2017-07-20T15:39:03.631297Z" },
"cells" : [ ]
}
]
}
This is a bug, cqlsh is displaying the timestamp from partition 't' for
partition 'b'.
I've created https://issues.apache.org/jira/browse/CASSANDRA-13711 based on
your report. I havent yet verified if this is a cqlsh bug or a storage engine
bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org
