You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Eric Evans (JIRA)" <ji...@apache.org> on 2009/12/02 17:10:22 UTC

[jira] Created: (CASSANDRA-595) need serialVersionUID for Range

need serialVersionUID for Range
-------------------------------

                 Key: CASSANDRA-595
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-595
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 0.5
            Reporter: Eric Evans
            Assignee: Eric Evans
            Priority: Minor


Range implements Serializable solely to accommodate JMX (Cassandra serializes Ranges differently), and the serialVersionUID was left unset to communicate that we aren't providing any guarantees about the serialization format. This is very inconvenient however, because it means that JMX client applications must be from the same build to work.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CASSANDRA-595) need serialVersionUID for Range

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-595.
--------------------------------------

    Resolution: Fixed
      Assignee:     (was: Eric Evans)

stu snuck this into CASSANDRA-608

> need serialVersionUID for Range
> -------------------------------
>
>                 Key: CASSANDRA-595
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-595
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.5
>            Reporter: Eric Evans
>            Priority: Minor
>
> Range implements Serializable solely to accommodate JMX (Cassandra serializes Ranges differently), and the serialVersionUID was left unset to communicate that we aren't providing any guarantees about the serialization format. This is very inconvenient however, because it means that JMX client applications must be from the same build to work.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.