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

Migration from 1.13 over 2.0.5 to 2.1 fails #4991

Closed
danielmewes opened this issue Oct 23, 2015 · 3 comments
Closed

Migration from 1.13 over 2.0.5 to 2.1 fails #4991

danielmewes opened this issue Oct 23, 2015 · 3 comments
Assignees
Labels
Milestone

Comments

@danielmewes
Copy link
Member

Reported by a user in https://groups.google.com/forum/#!topic/rethinkdb/cynZc-_Z-DE

I could reproduce the problem by following his steps. I additionally created two tables on 1.13, one with a single index and one without indexes.

@danielmewes danielmewes added this to the 2.1.x milestone Oct 23, 2015
@danielmewes
Copy link
Member Author

Wow, actually this happens even without ever creating any table!

@Tryneus
Copy link
Member

Tryneus commented Oct 24, 2015

Fix is up in review 3298. Still no ideas on why this didn't happen before.

@Tryneus
Copy link
Member

Tryneus commented Oct 24, 2015

The fix has been approved and merged to next and v2.1.x in commits cb8f595 and b21ead6, respectively. Will be in release 2.1.6.

@Tryneus Tryneus closed this as completed Oct 24, 2015
@danielmewes danielmewes modified the milestones: 2.1.x, 2.2 Nov 10, 2015
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

2 participants