Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Retake – Open-Source Hybrid Search for Postgres

github.com

Post reply on HN
Print view View original

11–20 of 24 posts

Re: Show HN: Retake – Open-Source Hybrid Search for Postgres

#13

Post by pnoel »

pk19238 wrote: post #12

Does the sync handle deletes? In terms of we delete data from our Postgres database and it will delete from your database as well? Can see this integrating well with our pipeline since we're syncing data from postgres to our own vector database.

Yes it does :)

Re: Show HN: Retake – Open-Source Hybrid Search for Postgres

#14

Post by pnoel »

seemaze wrote: post #11

From the product landing page: "By connecting to your sources of truth, Retake unlocks real-time keyword and semantic search over siloed data" I misread 'siloed data' as 'soiled data' and was like, this product gets me!

Must be some dirty ETL pipelines :')

Re: Show HN: Retake – Open-Source Hybrid Search for Postgres

#16

Post by retakeming »

isaacfung wrote: post #10
pnoel wrote: post #7

Earlier quoted context omitted.

That's a nice diagram! Yeah that's roughly it. We'll be adding support for more sources of truth in the future to expand coverage, like the ones you mention but also NoSQL like MongoDB

So are you guys using faiss instead of the vector search of postgres? I think vespa also supports hybrid search(it can also use late interaction model like colbert). How is retake compared to vespa? Will retake supports sparse vector models like SPLADE(I heard they solve the vocab mismatch problems of keyword search). How do you guys implement filtering?

1. Correct - we don't rely on pgvector. As a result, we're compatible with more existing managed Postgres services.

2. Probably the biggest differentiator between Vespa and Retake is the core architecture - Retake is built on top of OpenSearch. There's been quite a bit of debate regarding different search engines since Yahoo released Vespa - we leaned into OpenSearch because we saw that Open/ElasticSearch and its query language was much more familiar to more developers. Something that's coming soon to Retake is the ability to control how keyword/semantic scores are normalized and combined, which should give developers more fine-tuned control over their results.

3. In the short term, our support for models like SPLADE is constrained by OpenSearch, which uses BM25. In the medium to long term we would definitely consider modifying OpenSearch to do stuff like this.

4. We support both post-filtering and efficient kNN filtering, which takes place during the kNN search and guarantees that k results are returned. More details on the faiss kNN filter implementation can be found on the OpenSearch docs: https://opensearch.org/docs/latest/search-plugins/knn/filter...

Re: Show HN: Retake – Open-Source Hybrid Search for Postgres

#17

Post by retakeming »

spleen7777 wrote: post #15

How it handles JSONB fields? Do I need to define all keys in JSONB field to make them indexed?

You don't need to define all keys in a JSON object - by default, new keys will automatically be added to the index mapping when a JSON document containing that key is added to the index.

Details on how to query JSON objects can be found in our docs: https://docs.getretake.com/search/object

Post reply on HN