mirror of
https://github.com/qdrant/landing_page.git
synced 2026-09-27 15:08:30 +02:00
43 lines
2.2 KiB
Markdown
43 lines
2.2 KiB
Markdown
---
|
|
title: Introducing Qdrant 0.11
|
|
short_description: Check out what's new in Qdrant 0.11
|
|
description: Replication support is the most important change introduced by Qdrant 0.11. Check out what else has been added!
|
|
preview_dir: /articles_data/qdrant-0-11-release/preview
|
|
small_preview_image: /articles_data/qdrant-0-11-release/announcement-svgrepo-com.svg
|
|
social_preview_image: /articles_data/qdrant-0-11-release/preview/social_preview.jpg
|
|
weight: 65
|
|
author: Kacper Łukawski
|
|
author_link: https://medium.com/@lukawskikacper
|
|
date: 2022-10-26T13:55:00+02:00
|
|
draft: false
|
|
---
|
|
|
|
We are excited to [announce the release of Qdrant v0.11](https://github.com/qdrant/qdrant/releases/tag/v0.11.0),
|
|
which introduces a number of new features and improvements.
|
|
|
|
## Replication
|
|
|
|
One of the key features in this release is replication support, which allows Qdrant to provide a high availability
|
|
setup with distributed deployment out of the box. This, combined with sharding, enables you to horizontally scale
|
|
both the size of your collections and the throughput of your cluster. This means that you can use Qdrant to handle
|
|
large amounts of data without sacrificing performance or reliability.
|
|
|
|
## Administration API
|
|
|
|
Another new feature is the administration API, which allows you to disable write operations to the service. This is
|
|
useful in situations where search availability is more critical than updates, and can help prevent issues like memory
|
|
usage watermarks from affecting your searches.
|
|
|
|
## Exact search
|
|
|
|
We have also added the ability to report indexed payload points in the info API, which allows you to verify that
|
|
payload values were properly formatted for indexing. In addition, we have introduced a new `exact` search parameter
|
|
that allows you to force exact searches of vectors, even if an ANN index is built. This can be useful for validating
|
|
the accuracy of your HNSW configuration.
|
|
|
|
## Backward compatibility
|
|
|
|
This release is backward compatible with v0.10.5 storage in single node deployment, but unfortunately, distributed
|
|
deployment is not compatible with previous versions due to the large number of changes required for the replica set
|
|
implementation. However, clients are tested for backward compatibility with the v0.10.x service.
|