cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mahesh Daksha <>
Subject Re: ***UNCHECKED*** Query regarding cassandra column write time set by client Timestamp Generator
Date Tue, 09 Apr 2019 09:26:07 GMT
Thanks Ben for your response.
WRITETIME  gives the information of about the column value already residing
int the table. We intend to know  the timestamp of the record which is
about to apply/update.
This is needed to understand the timestamp difference of the data residing
in table with the one going to overwite the same.

This all information is needed as out update statements going silent (not
reflecting any changes) in database. Not even returning any error or

Mahesh Daksha

On Tue, Apr 9, 2019 at 2:46 PM Ben Slater <>

> Not in the logs but I think you should be able to use the WRITETIME
> function to view via CQL (see
> Cheers
> Ben
> ---
> *Ben Slater*
> *Chief Product Officer*
> <>   <>
>    <>
> Read our latest technical blog posts here
> <>.
> This email has been sent on behalf of Instaclustr Pty. Limited (Australia)
> and Instaclustr Inc (USA).
> This email and any attachments may contain confidential and legally
> privileged information.  If you are not the intended recipient, do not copy
> or disclose its content, but please reply to this email immediately and
> highlight the error to the sender and then immediately delete the message.
> On Tue, 9 Apr 2019 at 16:51, Mahesh Daksha <> wrote:
>> Hello,
>> I have configured the timestamp generator at cassandra client as below:
>> cluster.setTimestampGenerator(new AtomicMonotonicTimestampGenerator());
>> My cassandra client inserting and updating few of the rows in a table.
>> My query is where in the cassandra debug logs I can see the query write
>> time associated by with updated columns in the update query (sent by
>> cient). Or if there is any other way I can log the same at client itself.
>> Basically I want to see the write time sent by client to cassandra
>> cluster.
>> Thanks,
>> Mahesh Daksha

View raw message