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

Message claims that secondary indexes are not dumped #3708

Closed
AtnNn opened this issue Jan 30, 2015 · 2 comments
Closed

Message claims that secondary indexes are not dumped #3708

AtnNn opened this issue Jan 30, 2015 · 2 comments
Assignees
@Tryneus
Milestone
1.16.1

Comments

@AtnNn
Copy link
Member

AtnNn commented Jan 30, 2015 

$ rethinkdb-dump
NOTE: 'rethinkdb-dump' only dumps data and does *not* dump secondary indexes or
 cluster metadata.  You will need to recreate your secondary indexes and cluster
 setup yourself after you run 'rethinkdb-restore'.
@AtnNn AtnNn added this to the 1.16.x milestone Jan 30, 2015
@Tryneus
Copy link
Member

Tryneus commented Jan 30, 2015

The fix is up in review 2560. Changed the message to mention that the dump includes secondary indexes. Also included output in the export script, the line 5422 rows exported from 3 tables would now be 5422 rows exported from 3 tables, with 2 secondary indexes.

@Tryneus
Copy link
Member

Tryneus commented Jan 31, 2015

This has been approved and merged to next in commit 4587199, and cherry-picked into v1.16.x in commit 4442d7d. Since this is a python driver change and non-critical (log statements only) - it will probably not be released until 1.16.1, but we'll see.

@Tryneus Tryneus closed this as completed Jan 31, 2015
@AtnNn AtnNn modified the milestones: 1.16.x, 1.16.1 Feb 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Tryneus Tryneus

Labels
None yet
Projects
None yet
Milestone
1.16.1
Development

No branches or pull requests
2 participants
@Tryneus @AtnNn