Qdrant ES Gateway
An Elasticsearch-compatible application-search gateway backed by the Qdrant engine.
The project is aimed at teams that want to keep the Elasticsearch client and request shapes already embedded in an application while using Qdrant for the search and storage engine underneath.
Start here
This is an application-search gateway, not a drop-in replacement for Kibana, log analytics, Lucene scoring, or every Elasticsearch administration API.
Posts
-
Releases should not depend on remembering three version files
-
0.1.2: safer defaults for production traffic
-
A missing update is not an upsert
-
A missing delete is not a successful delete
-
A timeout is a feature
-
Oversized requests are not bad JSON
-
A missing document is a 404
-
One replica is the safe default
-
No phantom indices after creation failures
-
A slash is part of the document ID
-
When bulk errors did not mean errors
-
Three nodes, one disappears, and the search keeps moving
-
Making the bulk request limit real
-
Keep the Elasticsearch client, change the engine
-
Two collections, one stateless gateway
-
Pattern queries without a client rewrite
-
Batching searches and paging through ordered results
-
Compatibility includes the boring lifecycle calls
-
Launch video: keep the Elasticsearch client, change the engine
-
A dress, a tea bag, and a null
subscribe via RSS