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

Cannot start kuzu_shell with existing data (database path) #1405

Closed
uwegeercken opened this issue Mar 22, 2023 · 3 comments
Closed

Cannot start kuzu_shell with existing data (database path) #1405

uwegeercken opened this issue Mar 22, 2023 · 3 comments

Comments

@uwegeercken
Copy link

I just built kuzu from src.

Compiling went well, but when I wanted to start kuzu_shell with the usual -i flag for the database path I get an error:

Flag could not be matched: 'i'
  ./kuzu_shell databasePath {OPTIONS}

    KuzuDB Shell

  OPTIONS:

      databasePath                      Database path.
      -h, --help                        Display this help menu
      -d, --defaultBPSize               Size of buffer pool for default and
                                        large page sizes in megabytes
      "--" can be used to terminate flag options and force all following
      arguments to be treated as positional options

Note that the database path already contains data from the kuzu 0.2 version!

Running kuzu_shell without the -i also does not work (with an existing db pat)::

./kuzu_shell /home/uwe/development/kuzu-db
Opened the database at path: /home/uwe/development/kuzu-db
Enter ":help" for usage hints.
std::bad_alloc

The client immediately exits.

But running kuzu_shell on an empty directory works:

./kuzu_shell /home/uwe/development/kuzu-db2
Opened the database at path: /home/uwe/development/kuzu-db2
Enter ":help" for usage hints.
kuzu>
@andyfengHKU
Copy link
Contributor

Hi @uwegeercken,

This is desired behaviour. Because we are iterating quickly and constantly modifying storage format. We cannot provide backward compatibility between different versions. This will be the case for a while until we stabilize on the storage side.

Thanks,
Xiyang

@uwegeercken
Copy link
Author

Yes, I thought so. I wanted to add it here so that others see the issue as well.

Thanks,

Uwe

@andyfengHKU
Copy link
Contributor

PR #1436 has introduced storage format number so we throw error message if storage version is not aligned with kuzu binary version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants