Live data from Hacker News

Qdrant 1.7.0

qdrant.tech

31–32 of 32 posts

Re: Qdrant 1.7.0

#31

Qdrant is the vectordb that ChatGPT and Grok use (e.g. when you add docs to a custom GPT or tweets in Grok) https://twitter.com/simonw/status/1722011967886688696

Interesting they both do. Does Qdrant look like a winning horse then? Was about to use Weaviate for a project today and this gives me pause. Anyone have some strong opinions? pg_vector also been on my radar recently. Qdrant vs Weaviate I know is partially a rust vs go topic.

(disclosure: I work at Weaviate) I think it depends on your use-case. From what I've seen, Weaviate and Qdrant have similar offerings in terms of features, open-sourceness, flexible deployment, and integrations with other services. Weaviate does provide certain things easier to set up, like built-in hybrid search, modules for integrations, vectorization, etc. (so it's just a one-line config change), and it's all custom-built from the ground up. But Qdrant gets a lot of support from the Rust community and has a slightly more flexible free cloud tier.

Also, don't believe everything posted on the internet ;)

Re: Qdrant 1.7.0

#32
post #6

Just the other day I played with qdrant, using its Python client. Pretty smooth onboarding experience. I came across two questions. Perhaps some kind folks with more experience can shed some light on these qdrant use cases. 1. for embeddings for use cases such as LLM chat bots, I split internal data into chunks. Those chunks are then vectorized and stored. Alongside the entry itself, I stored the original chunk in me…

You can have a look at this sheet: https://docs.google.com/spreadsheets/d/170HErOyOkLDjQfy3TJ6a...

It shows which Vector DBs have a particular feature. "In-built Text Embeddings creation" is a column you can look at.

Post reply on HN