tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Poorna Chandra <poo...@apache.org>
Subject Tephra backwards compatibility
Date Thu, 12 May 2016 03:49:13 GMT

We found an issue when testing Tephra for backwards compatibility.
Transaction edit log sequence file persists the classname of the
transaction edit object. When an existing edit log is read using new Apache
Tephra jars, a class not found exception is thrown. Sequence file expects
to find the old version of Transaction Edit class -

Is it okay to have co.cask.tephra classes in Apache Tephra for backwards
compatibility purpose for the first few releases?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message