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

Sylvain Lebresne commented on CASSANDRA-3729:
---------------------------------------------

bq. Just to be clear, it's a per-client setting

I missed that, sorry. It does is better than a JMX setting then.

bq. Suppose we create a developer-only service that extends the public service?

I suppose some form of debug console (which could take the form of a separate 
thrift service + some debug shell to connect to it) wouldn't be a crazy idea if 
it's clearly separated from the public API. Feels like a bit of work for just 
getting counter contexts, but maybe we can find other uses for it (for 
instance, we could disable access to the system keyspace from the public API, 
but enable it from the debug "console").
                
> support counter debug mode on thrift interface
> ----------------------------------------------
>
>                 Key: CASSANDRA-3729
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3729
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Peter Schuller
>            Assignee: Peter Schuller
>            Priority: Minor
>         Attachments: trunk-3729.txt
>
>
> Attaching a patch against trunk to add a counter debug mode on the thrift 
> interface, allowing clients to decode and inspect counter contexts. This is 
> all Stu's code, except that I generated the thrift stuff so any mistakes 
> there are mine.
> This was extremely useful internally on an 0.8. The patch is not yet tested 
> on trunk, but if you think this can go in I will spend effort to test it 
> soonish.
> It's not very invasive (other than the generated thrift code), so it feels 
> okay to have it if we maybe document that it is not a supported interface 
> (clearly in the thrift spec).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to