Thanks to visit codestin.com
Credit goes to github.com

Skip to content

_restore not handling -i DB.TABLE #307

Closed
@srh

Description

@srh

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingnot qualifiedThe issue is not checked yet by the owners

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions