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.

Sign up for GitHub

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

Jump to bottom

core: introduce a way to test for bc breaks in datastore #193

Closed
aeneasr opened this issue Aug 9, 2016 · 3 comments
Closed

core: introduce a way to test for bc breaks in datastore #193

aeneasr opened this issue Aug 9, 2016 · 3 comments
Labels
feat New feature or request.
Milestone
unplanned

Comments

@aeneasr
Copy link
Member

aeneasr commented Aug 9, 2016

No description provided.

@aeneasr aeneasr added the feat New feature or request. label Aug 9, 2016
@aeneasr aeneasr added the debt label Aug 17, 2016
@aeneasr
Copy link
Member Author

aeneasr commented Aug 23, 2016

One way would be to:

  1. pull the latest image from dokerhub
  2. run it and connect it to rethinkdb
  3. run a few commands (every api at least once)
  4. kill the hydra image
  5. compile image from source
  6. run it against same rethinkdb
  7. run commands and see if they fail

@aeneasr
Copy link
Member Author

aeneasr commented Sep 23, 2016

I tested #193 (comment) on the 0.5.0 release and it worked quite well.

@aeneasr aeneasr changed the title introduce a way to test for bc breaks in rethinkdb core: introduce a way to test for bc breaks in datastore Oct 9, 2016
@aeneasr aeneasr added the other label Jun 5, 2017
@aeneasr
Copy link
Member Author

aeneasr commented Oct 5, 2017

I don't think this is relevant any more as we have the migrate command.

@aeneasr aeneasr closed this as completed Oct 5, 2017
@snyk-bot snyk-bot mentioned this issue Dec 3, 2021
Open
@snyk-bot snyk-bot mentioned this issue Jan 13, 2022
Open
@snyk-bot snyk-bot mentioned this issue Feb 10, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feat New feature or request.
Projects
None yet
Milestone
unplanned
Development

No branches or pull requests
1 participant
@aeneasr