<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>检索 on Plbear | 后端架构 · AI工程 · 云原生技术博客</title><link>https://www.plbear.com/tags/%E6%A3%80%E7%B4%A2/</link><description>Recent content in 检索 on Plbear | 后端架构 · AI工程 · 云原生技术博客</description><generator>Hugo</generator><language>zh-cn</language><lastBuildDate>Wed, 20 May 2020 09:00:00 +0800</lastBuildDate><atom:link href="https://www.plbear.com/tags/%E6%A3%80%E7%B4%A2/index.xml" rel="self" type="application/rss+xml"/><item><title>ES 父子文档：为什么我弃用了 Nested</title><link>https://www.plbear.com/posts/2020-05-20-es-parent-join-vs-nested/</link><pubDate>Wed, 20 May 2020 09:00:00 +0800</pubDate><guid>https://www.plbear.com/posts/2020-05-20-es-parent-join-vs-nested/</guid><description>简历搜索里最纠结的建模选择：Nested 好写但改一个子项要重索引整份文档，Parent-Join 灵活但要处理关联查询的开销。这篇文章记录我从 Nested 迁到 Parent-Join 的真实决策过程。</description></item></channel></rss>