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

[docs] Update Storage Documentation #1392

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[docs] Update Storage Documentation #1392

wants to merge 1 commit into from

Conversation

davidmyriel
Copy link
Contributor

No description provided.

Copy link

netlify bot commented Jan 16, 2025

Deploy Preview for condescending-goldwasser-91acf0 ready!

Name Link
🔨 Latest commit ffc7370
🔍 Latest deploy log https://app.netlify.com/sites/condescending-goldwasser-91acf0/deploys/678860f218ac1600082f881e
😎 Deploy Preview https://deploy-preview-1392--condescending-goldwasser-91acf0.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Member

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.
Copy link
Member

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.


Suggested change
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.

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

Successfully merging this pull request may close these issues.

3 participants