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

Nick Bailey commented on CASSANDRA-2805:
----------------------------------------

I'm probably going to take this and try and get it done quickly before the 1.0 
freeze. I'd really like to solve this problem before 1.0 and then be strict on 
preventing this in future mbean methods.

> Clean up mbeans that return Internal Cassandra types
> ----------------------------------------------------
>
>                 Key: CASSANDRA-2805
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2805
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.8.1
>            Reporter: Nick Bailey
>            Assignee: Gaurav Sharma
>            Priority: Minor
>              Labels: lhf
>             Fix For: 1.0
>
>
> We need to clean up wherever we return internal cassandra objects over jmx. 
> Namely CompactionInfo objects as well as Tokens. There may be a few other 
> examples.
> This is bad for two reasons
> 1. You have to load the cassandra jar when querying these mbeans, which sucks.
> 2. Stuff breaks between versions when things are moved. For example, 
> CASSANDRA-1610 moves the compaction related classes around. Any code querying 
> those jmx mbeans in 0.8.0 is now broken in 0.8.2. (assuming those moves stay 
> in the 0.8 branch)
> For things like CompactionInfo we should just expose more mbean methods or 
> serialize to something standard like json.
> I'd like to target this for 0.8.2. Since we've already broken compatibility 
> between 0.8.0 and 0.8.1, I'd say just fix this everywhere now.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to