-
Notifications
You must be signed in to change notification settings - Fork 0
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
Reading RDB files #1
Comments
For better computational resources, check out the DANDI Hub. See if you can spin up the server there However, #2 is greatly preferred if at all possible. That way we can ensure completely lazy access at all times Wow, the repo has 700+ forks lol Did you check out this PR by someone's fork that extended the version? sripathikrishnan/redis-rdb-tools#186 |
Also curious is https://pypi.org/project/rdb-cli/ allows you do extract every data stream and map it to JSON (either a pre-step to get a JSON version of the file, or if there are utility functions for parsing contents via an API?) |
They only alter the version checking requirement but don't actually make any changes to to the parser. I tried using that fork and ran into an error with one of the data entries. Haven't had a chance to dig into that error though.
According to the package description, this is forked from |
Quick update:
|
OK, (1) can work then if we can confirm that is how they are used to running the system; can you check with them on that? |
Yeah sure! Could you (or Ben) loop me in on the email thread? |
Ok, so we'll move ahead with running a Redis server and querying through their official Python interface, since the Stavisky lab should have the server running (or can easily get it running) whenever they use our conversion scripts. Closing this for now... |
From what I can tell there are two ways to read data from RDB files:
If this is a tool they want to use themselves, then probably best to go with option 1. In that case, best step might be to ask them for a smaller RDB file?
The text was updated successfully, but these errors were encountered: