Skip to content

_restore not handling -i DB.TABLE #307

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

Closed
srh opened this issue Nov 10, 2023 · 0 comments · Fixed by #308
Closed

_restore not handling -i DB.TABLE #307

srh opened this issue Nov 10, 2023 · 0 comments · Fixed by #308
Labels
bug Something isn't working not qualified The issue is not checked yet by the owners

Comments

@srh
Copy link
Contributor

srh commented Nov 10, 2023

When attempting to use -i DB.TABLE, we get "Error: Archive file had no files" consistently.

Using -i DB works fine.

$ python3 _dump.py -e test.marvel -f marv.tar.gz
            NOTE: 'rethinkdb-dump' saves data, secondary indexes, and write hooks, but does *not* save
            cluster metadata.  You will need to recreate your cluster setup yourself after
            you run 'rethinkdb-restore'.
  Exporting to temporary directory...
    [========================================] 100%
    1 row exported from 1 table, with 0 secondary indexes, and 0 hook functions
  Zipping export directory...
Done (0.23 seconds): /home/srh/sw/rethinkdb-python/marv.tar.gz
$ tar -tf marv.tar.gz 
rethinkdb_dump_2023-11-10T06:46:50/test/marvel.json
rethinkdb_dump_2023-11-10T06:46:50/test/marvel.info
$ python3 _restore.py marv.tar.gz -i test.marvel
Extracting archive file...
Error: Archive file had no files
$ python3 _restore.py marv.tar.gz -i test
Extracting archive file...
  Done (0 seconds)
Importing from directory...
  [========================================] 100%
  1 row imported to 1 table in 0.78 secs

System info
I ran this on Ubuntu 22.04 with the tip of the rethinkdb-python repository and v2.4.x.

A user on Slack encountered this problem with some other versions.

@srh srh added bug Something isn't working not qualified The issue is not checked yet by the owners labels Nov 10, 2023
@srh srh closed this as completed in #308 Nov 10, 2023
@srh srh mentioned this issue Nov 10, 2023
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working not qualified The issue is not checked yet by the owners
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant