-
Notifications
You must be signed in to change notification settings - Fork 82
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
[docs] Update Storage Documentation #1392
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for condescending-goldwasser-91acf0 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Qdrant Collection -> Collection Shard
@@ -7,19 +7,23 @@ aliases: | |||
|
|||
# Storage | |||
|
|||
All data within one collection is divided into segments. | |||
Each segment has its independent vector and payload storage as well as indexes. | |||
In a Qdrant collection, all data is divided into **segments**. Each segment contains several components: **vector** and **payload storages** as well as **vector** and **payload indexes**. Behind the scenes, each segment has an ID mapper that links internal and external IDs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also here, there's a layer in between.
Collections have shards. There may be multiple copies of shards, which we call replicas. Shards have segments.
We normally mostly abstract this concept away, and segments aren't visible on the logical data level.
I understand we might want to describe segments somewhere, but describing it in the optimizer section may be better. They're closely related to the optimization process.
In a Qdrant collection, all data is divided into **segments**. Each segment contains several components: **vector** and **payload storages** as well as **vector** and **payload indexes**. Behind the scenes, each segment has an ID mapper that links internal and external IDs. | |
In a Qdrant shard, all data is divided into **segments**. Each segment contains several components: **vector** and **payload storages** as well as **vector** and **payload indexes**. Behind the scenes, each segment has an ID mapper that links internal and external IDs. |
No description provided.