[
https://issues.apache.org/jira/browse/ACCUMULO-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955775#comment-13955775
]
Sean Busbey commented on ACCUMULO-2598:
---------------------------------------
Sure, but it will be easier to plan for and handle those changes with graceful
failure if we don't have to contend with ClassNotFoundException as a part of it.
> Update Fate to avoid serializing classnames
> -------------------------------------------
>
> Key: ACCUMULO-2598
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2598
> Project: Accumulo
> Issue Type: Improvement
> Components: fate
> Affects Versions: 1.4.5, 1.5.1, 1.6.0
> Reporter: Sean Busbey
> Priority: Minor
> Labels: rolling_upgrade
> Fix For: 1.7.0
>
>
> Fate in 1.4, 1.5, and 1.6 relies on serializing the class name for operations
> directly. This makes upgrades harder (and precludes rolling upgrades) because
> those class names can and have changed between major versions.
> Rather than adopting a policy around compatibility changes outside of hte
> public API, we should change how Fate is implemented so that this isn't an
> issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
