Thanks for the response. We'll keep some co.cask classes for backwards compatibility then.
Poorna. On Thu, May 12, 2016 at 12:46 AM, James Taylor <[email protected]> wrote: > I agree. We had to do something similar for our first Phoenix release - had > a kind of stub class that we removed in the next release. > > Thanks, > James > > On Wed, May 11, 2016 at 8:52 PM, Henry Saputra <[email protected]> > wrote: > > > AFAIK there is no rule to make class name as org.apache namespace. > > > > Usually it is being done to adhere with Apache branding and make it > easier > > to organize for client. > > > > For example, kafka maintain "kafka" as the root package name. > > > > So, should be ok for Tephra. > > > > - Henry > > > > On Wed, May 11, 2016 at 8:49 PM, Poorna Chandra <[email protected]> > wrote: > > > > > Hi, > > > > > > 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 - > > > co.cask.tephra.persist.TransactionEdit. > > > > > > Is it okay to have co.cask.tephra classes in Apache Tephra for > backwards > > > compatibility purpose for the first few releases? > > > > > > Thanks, > > > Poorna. > > > > > >
