Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does it make sense to try to retain storage compatibility with Akka <= 2.3.3? #13

Closed
rkuhn opened this issue Jan 30, 2016 · 4 comments
Closed
Labels
Milestone

Comments

@rkuhn
Copy link
Contributor

rkuhn commented Jan 30, 2016

With the removal of Channels and confirmations there are actual features that cannot any longer be expressed, meaning that the application code itself will have to change.

@patriknw @ktoso @sclasen what is your opinion?

@rkuhn rkuhn added this to the 1.0 milestone Jan 30, 2016
@rkuhn rkuhn added the question label Jan 30, 2016
@sclasen
Copy link
Contributor

sclasen commented Jan 30, 2016

+1 to not attempting to retain compatibility, the underlying layout will have to change to reflect the updated functionality in akka-persistence

@rkuhn
Copy link
Contributor Author

rkuhn commented Jan 31, 2016

Okay, then we’re going for a 1.0 version that clearly advertises no compatibility to 0.x versions.

@patriknw
Copy link
Member

patriknw commented Feb 1, 2016

+1 for making a clean cut, but if there are tooling around DynamoDB that makes it possible to do a ETL migration it is good to mention the possibility in some migration guide

@rkuhn
Copy link
Contributor Author

rkuhn commented Feb 3, 2016

Good, that’s settled then. Filed #21 for the migration guide.

@rkuhn rkuhn closed this as completed Feb 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants