[
https://issues.apache.org/jira/browse/CASSANDRA-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104568#comment-14104568
]
Tyler Hobbs commented on CASSANDRA-7021:
----------------------------------------
Since we don't save the original query text for prepared statements (and doing
so would use a fair amount of memory), the best option is to try to regenerate
the original query from CQLStatement instances. One downside to this is that
the regenerated query may not exactly match the original, making it more
difficult for users to match the trace to an application query.
> 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
> Components: Core
> Environment: C* 2.0.6 running on Ubuntu 12.04
> Reporter: Bill Joyce
> Assignee: Tyler Hobbs
> Priority: Minor
> Fix For: 2.0.10
>
>
> 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.2#6252)
