accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3132) Fate uses java serialization which is error-prone between upgrades
Date Thu, 08 Jan 2015 16:30:35 GMT

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

Christopher Tubbs commented on ACCUMULO-3132:
---------------------------------------------

It appears work was logged on this for 1.6.1, but it was never closed. The "fix" seems to
create a reproducibility issue in the build, as identified by ACCUMULO-3433's note that when
building for a release, the generated thrift files are clobbered.

> Fate uses java serialization which is error-prone between upgrades
> ------------------------------------------------------------------
>
>                 Key: ACCUMULO-3132
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3132
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.5.0, 1.5.1, 1.6.0
>            Reporter: Eric Newton
>             Fix For: 1.6.2, 1.7.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Fate uses java serialization to save objects to zookeeper.  If an upgrade is performed
while a Fate transaction is running, the data stored in Fate may not deserialize in the upgraded
software unless developers are very careful about the Repo's internals.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message