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

Migrate local json-based storage to jpa #2016

Closed
skabashnyuk opened this issue Aug 1, 2016 · 2 comments
Closed

Migrate local json-based storage to jpa #2016

skabashnyuk opened this issue Aug 1, 2016 · 2 comments
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Milestone

Comments

@skabashnyuk
Copy link
Contributor

skabashnyuk commented Aug 1, 2016

We need to migrate all data stored in json-based storage to jpa database

Important thing here is how we will do that. There is two options

  • As component of che
  • As separate tool

There is couple of pros and cons in both ways

  • Component is part of the che. User don't need to download anything . Everything will happen automatically
  • We don't want to keep this code for long time. Ideally remove it in release after. So separate tool is better.
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. sprint/next team/platform labels Aug 1, 2016
@skabashnyuk
Copy link
Contributor Author

@TylerJewell do you have a vision what is better of user and for us?
For instance can we tell user who has json-base storage and wants to migrate data to run some particular predefined version of che first and then run the latest version of che? In this case we will keep migration code only in first jpa based version of che
wdyt?

@TylerJewell
Copy link

@skabashnyuk - I don't see how that could be really good for the user. Is there any way we could ship a couple different migrations:
1: If you have version x, then the migration is automatic.
2: If you have version x-1, x-2, then we have an internal migration up to x, and then migrate to JPA
3. If you have version x-3, we do not support migration.

@skabashnyuk skabashnyuk mentioned this issue Aug 2, 2016
15 tasks
@skabashnyuk skabashnyuk added sprint/current status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. and removed sprint/next labels Aug 4, 2016
@voievodin voievodin added the status/in-progress This issue has been taken by an engineer and is under active development. label Aug 5, 2016
@voievodin voievodin self-assigned this Aug 5, 2016
@bmicklea bmicklea removed the status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. label Aug 9, 2016
@voievodin voievodin added status/pending-merge and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Aug 11, 2016
@bmicklea bmicklea added this to the 5.0.0-M2 milestone Sep 13, 2016
@riuvshin riuvshin modified the milestones: 5.0.0-M3, 5.0.0-M2 Sep 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

No branches or pull requests

5 participants