[
https://issues.apache.org/jira/browse/CASSANDRA-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125534#comment-13125534
]
Nick Bailey commented on CASSANDRA-2805:
----------------------------------------
I agree my main argument though is that we have a history of doing it
unknowingly. Especially something like this where any update the the
CompactionInfo requires updating the serialization version and then breaks
compatibility.
I suppose I can live with this in 1.1 and a 'let's try really really really
hard not to break compatibility in the 1.0.x releases.
> 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.1
>
>
> 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.
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
