cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7021) With tracing enabled, queries should still be recorded when using prepared and batch statements
Date Wed, 27 Jul 2016 17:00:26 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395987#comment-15395987
] 

Robert Stupp commented on CASSANDRA-7021:
-----------------------------------------

Yes, CASSANDRA-11425 added the CQL text and CASSANDRA-11719 added the bind variables to trace.
This works at least for prepared statements. Need to check whether it works for prepared batch
statements, too. (It should, but did not test it yet.)

> With tracing enabled, queries should still be recorded when using prepared and batch
statements
> -----------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7021
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7021
>             Project: Cassandra
>          Issue Type: Improvement
>         Environment: C* 2.0.6 running on Ubuntu 12.04
>            Reporter: Bill Joyce
>            Priority: Minor
>             Fix For: 2.1.x
>
>
> I've enabled tracing on my cluster and am analyzing data in the system_traces.sessions
table. Single statement, non-prepared queries show up with data in the 'parameters' field
like 'query=select * from tablename where x=1' and the request field is execute_cql3_query.
But batches have null in the parameters field and prepared statements just have 'page size=5000'
in the parameters field (the request field values are 'Execute batch of CQL3 queries' and
'Execute CQL3 prepared query'). Please include the actual query text with prepared and batch
statements. This will make performance analysis much easier so I can do things like sort by
duration and find my most expensive queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message