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

Implement sub-databases as namespaces #147

Open
oleiade opened this issue Apr 30, 2013 · 2 comments
Open

Implement sub-databases as namespaces #147

oleiade opened this issue Apr 30, 2013 · 2 comments

Comments

@oleiade
Copy link
Owner

oleiade commented Apr 30, 2013

In order to reduce unpredictable disk seeks, my intuition is that the ability to create namespaces englobing databases would help.

For example, creating the namespace mynamespace would actually create a leveldb backend on the disk with that name. And then creating a db mydb inside mynamespace would make every operations over mydb being written in mynamespace physical backend with a mydb: prefix key.

@wbolster
Copy link

Note that Plyvel provides transparent support for the 'sub-databases' you describe using its PrefixedDB API. It handles all operations (get, put, delete, iterators, and so on).

@oleiade
Copy link
Owner Author

oleiade commented Jul 31, 2013

Hi @wbolster

I saw that feature pass yes, but Elevator has been completely rewritten in Go language, so I'm not using plyvel anymore. I guess I will have to code it myself :D 👯

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

No branches or pull requests

2 participants