Hello,
I sent this message a few days ago, but it seems to have gotten lost (I
don't see it on the archive), so I am trying again.
-
I am using Cassandra for some academic-type work that involves some
hacking of replica placement, etc. and I am observing a strange behavior
(well, strang
Timestamps are part of the ColumnFamily objects and their Columns,
contained in the RowMutation.
On Wed, Oct 24, 2012 at 2:57 PM, William Katsak wrote:
> Hello,
>
> I sent this message a few days ago, but it seems to have gotten lost (I
> don't see it on the archive), so I am trying again.
>
> --
Here is what I am seeing on each replica node. This is after a write
with consistencylevel=ALL.
DEBUG [MutationStage:48] 2012-10-24 16:56:01,050
RowMutationVerbHandler.java (line 56) RowMutation(keyspace='normal',
key='746573746b65793337', modifications=[ColumnFamily(data
[636f6c:false:3@1351
How are you doing the write? CQL or Thrift? In thrift, the client specifies
the timestamp, and you should always be seeing that as the timestamp. In CQL,
the CQL layer on the server adds the timestamp. I am less familiar with the
CQL code, maybe something screwy is going on there. 1.1.6 is
