[
https://issues.apache.org/jira/browse/CASSANDRA-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458746#comment-13458746
]
David Alves commented on CASSANDRA-4584:
----------------------------------------
bq. But honestly I'm not sure there is a point in disallowing tracing for some
query, especially since that's more work than doing it for all queries.
Besides, for any query it could be interesting to know how long it took to
parse it, to validate it and to execute it.
I see no reason why tracing should not be enabled for schema querying/altering
statements, but since "trace" is keyword we only know wether to trace *after*
we parse the query, which will make it difficult to track parse times.
> Add CQL syntax to enable request tracing
> ----------------------------------------
>
> Key: CASSANDRA-4584
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4584
> Project: Cassandra
> Issue Type: Sub-task
> Affects Versions: 1.2.0 beta 1
> Reporter: Jonathan Ellis
> Assignee: David Alves
> Fix For: 1.2.0
>
> Attachments: 4584.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
