You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ryan McGuire (JIRA)" <ji...@apache.org> on 2013/06/20 07:16:23 UTC
[jira] [Updated] (CASSANDRA-5672) Add enumumerated column to
system_trace.events table to signify the type of event.
[ https://issues.apache.org/jira/browse/CASSANDRA-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McGuire updated CASSANDRA-5672:
------------------------------------
Description:
Tracing of queries is useful for at least two different purposes:
* Interactively diagnosing a problem, via cqlsh, by a human.
* Programatically recording and responding to how queries behave.
This second purpose is not well suited to how the system_trace.events table is currently organized, as the only identifying characteristic of each event is a free-form string that can (and has) been changed in later versions.
[~jbellis] [mentioned the possibility|http://www.datastax.com/dev/blog/advanced-request-tracing-in-cassandra-1-2] of adding an enumeration of event types that would be immutable.
Reference [this dtest](https://github.com/riptano/cassandra-dtest/pull/13/files) that parses the strings in this table via regex. If these strings change, this test will break.
was:
Tracing of queries is useful for at least two different purposes:
* Interactively diagnosing a problem, via cqlsh, by a human.
* Programatically recording and responding to how queries behave.
This second purpose is not well suited to how the system_trace.events table is currently organized, as the only identifying characteristic of each event is a free-form string that can (and has) been changed in later versions.
[~jbellis] [mentioned the possibility](http://www.datastax.com/dev/blog/advanced-request-tracing-in-cassandra-1-2) of adding an enumeration of event types that would be immutable.
Reference [this dtest](https://github.com/riptano/cassandra-dtest/pull/13/files) that parses the strings in this table via regex. If these strings change, this test will break.
> Add enumumerated column to system_trace.events table to signify the type of event.
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-5672
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5672
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Ryan McGuire
> Priority: Minor
>
> Tracing of queries is useful for at least two different purposes:
> * Interactively diagnosing a problem, via cqlsh, by a human.
> * Programatically recording and responding to how queries behave.
> This second purpose is not well suited to how the system_trace.events table is currently organized, as the only identifying characteristic of each event is a free-form string that can (and has) been changed in later versions.
> [~jbellis] [mentioned the possibility|http://www.datastax.com/dev/blog/advanced-request-tracing-in-cassandra-1-2] of adding an enumeration of event types that would be immutable.
> Reference [this dtest](https://github.com/riptano/cassandra-dtest/pull/13/files) that parses the strings in this table via regex. If these strings change, this test will break.
--
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