You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 12, 2023. It is now read-only.
I happened to delete a TileDB workspace directory with a normal rm. It still appeared in the output from tiledb_ls_workspaces but any calls to that workspace gave an error including trying to create the workspace again. In the end, I ended up deleting .tiledb which probably shouldn't be the solution very often. Would it make sense to have a function that brings .tiledb into a "correct" state or how should I handle the situation after a folder has been deleted outside TileDB.
The text was updated successfully, but these errors were encountered:
The quick fix would be to re-create the workspace and delete it properly with tiledb_delete. I have tried this and it works without problems. Please let me know what error it gives you.
Regardless of the above though, your suggestion for having a "correction" function for .tiledb is nice and relatively easy to implement. I will keep the issue open and implement it soon.
Thanks!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I happened to delete a TileDB workspace directory with a normal
rm
. It still appeared in the output fromtiledb_ls_workspaces
but any calls to that workspace gave an error including trying to create the workspace again. In the end, I ended up deleting.tiledb
which probably shouldn't be the solution very often. Would it make sense to have a function that brings.tiledb
into a "correct" state or how should I handle the situation after a folder has been deleted outside TileDB.The text was updated successfully, but these errors were encountered: