krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-04 02:18:29 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1732 from qdrant/add_faq

Browse Source 
Add FAQs
This commit is contained in:
Derrick Mwiti
2025-06-27 13:46:48 +03:00
committed by GitHub
parent a79969192c 6539429334
commit e868adfc0f
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/faq/qdrant-fundamentals.md
+11
View File
@@ -135,6 +135,17 @@ data is automatically migrated to the newer storage format. This migration is no
We only guarantee compatibility if you update between consecutive versions. You would need to upgrade versions one at a time: `1.1 -> 1.2`, then `1.2 -> 1.3`, then `1.3 -> 1.4`.
### Should I create payload indexes before or after uploading?
Create payload indexes before uploading to avoid index rebuilding. However, there are scenarios where defining idexes after uploading is okay. For example, you can configure a new filter logic after launch.
You should always index first if you know your filters upfront. If you need to index another payload later, you can still do it, but be aware of the performance hit.
## Should I create one Qdrant collection per user?
No. Creating one collection per user is more resource intensive.
Instead of creating separate collections for each user, we recommend creating a [single collection](https://qdrant.tech/documentation/guides/multiple-partitions/) and separate access using payloads. Each Qdrant point can have a payload as metadata. For multitenancy, you can include a `user_id` or `tenant_id` for each point. To optimize storage further, you can enable [tenant indexing](https://qdrant.tech/documentation/concepts/indexing/#tenant-index) for payload fields.
## Cloud
### Is it possible to scale down a Qdrant Cloud cluster?