HorizonDB, a geocoding engine in Rust that replaces Elasticsearch

Re:HorizonDB, a geocoding engine in Rust that replaces Elast... by whakim on Monday August 11, 2025 @02:18AM (#44861213)

* Filterable ANN certainly decomposes into pre- and post-filtering, and there is definitely a lot of interesting innovation occurring around filterable ANN. But large-scale search systems currently do a pretty good job with pre-filtering, falling back to brute force search in the case of restrictive filters.

* You'd have to be a bit more exact re: dynamic updates/versioning for me to understand the challenges you're facing.

* Building graph indices can be slow, but in my experience (billions of embeddings) it is possible to build HNSW indices in tens of minutes.

* How is this any different to combining traditional keyword search with, say, recency boosting?

[ Parent | on HN ]

Re:HorizonDB, a geocoding engine in Rust that replaces Elast... by cfors on Monday August 11, 2025 @08:24AM (#44863387)

Might be missing my argument here - I stated that there are workable solutions to this like you have pointed out.

But ANN search is still a sledgehammer and building out hybrid solutions that help bridge the gap between this and traditional data stores still have room for innovation.

[ Parent | on HN ]

Re:HorizonDB, a geocoding engine in Rust that replaces Elast... by whakim on Monday August 11, 2025 @09:10PM (#44871262)

Fair enough - agreed there's lots of interesting innovations here - but my point is that semantic search and its associated issues don't really differ that much from other types of search problems at scale, and I therefore don't think that the current crop of vector database products add a lot of value from a technical perspective (perhaps they do from an ease-of-use perspective; or they work great at small scale, etc. etc.)

[ Parent | on HN ]