From user-return-63623-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org Tue Apr 9 09:31:10 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 952A3180629 for ; Tue, 9 Apr 2019 11:31:09 +0200 (CEST) Received: (qmail 9964 invoked by uid 500); 9 Apr 2019 09:11:24 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 9954 invoked by uid 99); 9 Apr 2019 09:11:24 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2019 09:11:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 67A02C1BFC for ; Tue, 9 Apr 2019 09:31:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.553 X-Spam-Level: * X-Spam-Status: No, score=1.553 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.257, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=instaclustr.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 3SJwQlEjCwhM for ; Tue, 9 Apr 2019 09:30:58 +0000 (UTC) Received: from mail-it1-f180.google.com (mail-it1-f180.google.com [209.85.166.180]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id DF3885FE45 for ; Tue, 9 Apr 2019 09:30:57 +0000 (UTC) Received: by mail-it1-f180.google.com with SMTP id y134so3760575itc.5 for ; Tue, 09 Apr 2019 02:30:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instaclustr.com; s=instaclustr.email.auth; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ylRVFCMTfjnH+BIaSPyCNO0vo4/gQC/PArzqdRsCTr0=; b=HV3xZQ70Wfl2KoqjUIkVXyvVvNatgl///+4NjTdZgwm2gdcBvviWFoalnBrtAesLGD HgGXcJet2qbG7KT+KTHNDD2tJmphSYvgk6YwShhaCYdKQXP9/UqKvr8AXGUgnIl7xWyZ Kp/731vJKpPS+4Zx1UW1ZQIViDEH7EtKp7yhA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ylRVFCMTfjnH+BIaSPyCNO0vo4/gQC/PArzqdRsCTr0=; b=i2jp0DdkMmDwEJGZQZxoG7Tz24ddYPJ6YRpupncg8hGBHGTv8XQqg/hcY6SzX+FOtX Jrex0+VWrMvwTl/mVbmDiMkErPtwUpMxZsT0rpx/6IftU6iFqVfuiroELVAV0oOeke6w 3tVmNK318pQEAyX1lzppba7EWandXwbt5QfRulCZZpvdBgYGSMUWNBUs6Jn/3lYNLI+I q2rlzwJiuwcKT/hXPdmfyQUOyPocDf334m7dsUTYcDoeDK4VRBq83nI5p+z49aza6lAX U8K8COlHug4ttkNvbtXL02nXXYp88rrswCAYahbRxCSSbWZjsWo8t1TsjedaV1hoZM+C ad4Q== X-Gm-Message-State: APjAAAU3G8ccGozoKkFCXVJR6GdzuqZcCv+YZqvVKbNYB/QK2U62Clny CknY+tes3FpfzXeMDWwjCcJ9mnSt/rHtUgxW/aultzt7N1bi7Q== X-Google-Smtp-Source: APXvYqz+FwOsf0+lMWvSb69Sps28UEOdvkx39dqUrx3z0w8/rBDvY0jghWHcOte2BVm8vbx0W2+AW7HqmWh8McmQ0o8= X-Received: by 2002:a02:7f90:: with SMTP id r138mr1047854jac.94.1554802257193; Tue, 09 Apr 2019 02:30:57 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ben Slater Date: Tue, 9 Apr 2019 19:30:45 +1000 Message-ID: Subject: Re: ***UNCHECKED*** Query regarding cassandra column write time set by client Timestamp Generator To: Cassandra User Content-Type: multipart/alternative; boundary="0000000000003c7f5a0586159c7d" --0000000000003c7f5a0586159c7d Content-Type: text/plain; charset="UTF-8" Maybe stabledump can help you? https://cassandra.apache.org/doc/4.0/tools/sstable/sstabledump.html --- *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 19:26, Mahesh Daksha wrote: > 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 > exception. > > Thanks, > Mahesh Daksha > > On Tue, Apr 9, 2019 at 2:46 PM Ben Slater > wrote: > >> Not in the logs but I think you should be able to use the WRITETIME >> function to view via CQL (see >> https://cassandra.apache.org/doc/latest/cql/dml.html#select) >> >> 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 >>> >> --0000000000003c7f5a0586159c7d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Tue, 9 Apr 2019 at 19:26, Mahesh Daksha= <dakshme@gmail.com> wrote:<= br>
Thanks Ben for your response.WRITETIME=C2=A0=C2=A0gives the information of about the column value alre= ady residing int the table. We intend to know=C2=A0 the timestamp of the re= cord 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) i= n database. Not even returning any error or exception.

=
Thanks,
Mahesh Daksha

On Tue, Apr 9, 2019 at 2:46 PM Be= n Slater <ben.slater@instaclustr.com> wrote:
Not in the logs but I think you should be able= to use the WRITETIME function to view via CQL (see=C2=A0https://cassandra.apache.org/doc/latest= /cql/dml.html#select)

= Cheers
Ben

---=C2=A0

Ben Slater
Chief Product Officer


=

=C2=A0=C2=A0=C2=A0=C2=A0

Read our latest technical blog posts=C2=A0here.

This email has been sent on behalf of=C2=A0Instaclustr Pty. Limited = (Australia) and=C2=A0Instaclustr Inc (USA).

This email and any attachment= s may=C2=A0contain confidential and legally privileged=C2=A0information.=C2= =A0 If you are not the intended=C2=A0recipient, do not copy or disclose its= =C2=A0content, but please reply to this email=C2=A0immediately and highligh= t the error to the=C2=A0sender and then immediately delete the=C2=A0message= .



On Tue, 9 Apr 2019 at 16:51, Mahesh Daksha <dakshme@gmail.com> wrote:
Hello,

I have configured th= e timestamp generator at cassandra client as below:

cluste= r.setTimestampGenerator(new AtomicMonotonicTimestampGenerator());=C2= =A0=C2=A0

My cassandra client inserting and up= dating few of the rows in a table.
My query is= where in the cassandra debug logs I can see the query write time associate= d by with updated columns in the update query (sent by cient). Or=C2=A0if there is any other way I can log the same at cli= ent itself.

Basically I want to see the write time sent by client to cassandra clus= ter.

Thanks,
Mahesh Daksha
--0000000000003c7f5a0586159c7d--