<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vector Search on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/vector-search/</link><description>Recent content in Vector Search on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 06 May 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/vector-search/index.xml" rel="self" type="application/rss+xml"/><item><title>Alibaba Cloud Full Stack (9): OpenSearch and AI Search</title><link>https://www.chenk.top/en/aliyun-fullstack/09-opensearch/</link><pubDate>Wed, 06 May 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/aliyun-fullstack/09-opensearch/</guid><description>&lt;p>I built my first search engine with Elasticsearch and a pile of synonyms. It took six months to get decent results. Every week, users complained about missing results, so I added more synonyms, broke something else, and added exception rules. The relevance tuning spreadsheet grew to 400 rows. I had custom analyzers for three languages, a boosting config that no one understood (including me), and a reindexing job that took four hours. Then I tried hybrid vector+keyword search on a side project and got better results on day one. Not marginally better — &amp;ldquo;users stopped complaining&amp;rdquo; better. That experience completely changed how I think about search, and it&amp;rsquo;s the reason this article exists.&lt;/p></description></item></channel></rss>