[ 
https://issues.apache.org/jira/browse/CASSANDRA-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

C. Scott Andreas updated CASSANDRA-5672:
----------------------------------------
    Component/s: Observability

> 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
>          Components: Observability
>    Affects Versions: 1.2.0
>            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 was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to