Skip to content

Update vinyl terminology in intro #48

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

Closed
kostja opened this issue Sep 6, 2016 · 0 comments
Closed

Update vinyl terminology in intro #48

kostja opened this issue Sep 6, 2016 · 0 comments
Assignees

Comments

@kostja
Copy link
Contributor

kostja commented Sep 6, 2016

https://tarantool.org/doc/intro.html:

Tarantool's disk-based storage engine is a fusion of ideas from modern filesystems, log-structured merge trees and classical B-trees. All data is organized into runs. Each run is represented by a file on disk. Run size is a configuration option and normally is around 64MB. Each run is a collection of pages, serving different purposes. Pages in a fully merged run contain non-overlapping ranges of keys. A run can be partially merged if there were a lot of changes in its key range recently. In that case some pages represent new keys and values in the run. The disk-based storage engine is append only: new data never overwrites old data. The disk-based storage engine is named vinyl.

We actually use the word "range" now for this. So, s/run/range/ in this paragraph.

On the same token, it's better to move and split this paragraph:

Tarantool supports multi-part index keys. The possible index types are HASH, TREE, BITSET, and RTREE.
To notimply that vinyl supports HASH, BITSET or RTREE.

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