<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: bimbobruno</title><link>https://news.ycombinator.com/user?id=bimbobruno</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 29 Apr 2026 10:48:46 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=bimbobruno" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Ask HN: How do you solve aggregation when agentic RAG breaks down?]]></title><description><![CDATA[
<p>I keep hitting the same failure mode with agentic RAG over collections of similar PDFs, like monthly electricity and gas bills from the same utility provider.<p>It works well for retrieval:
“Find my gas bill from January.”<p>Though even there similarity can be brittle. If I don’t specify the year, retrieval may surface the wrong January because multiple documents look nearly identical.<p>It really breaks down for aggregation:
“How much did I spend on electricity and gas last year?”
“Which months had the highest energy costs?”<p>At that point the problem feels misaligned with similarity search itself. You don’t want relevant chunks, you want structured values aggregated across documents.<p>Curious how people solve this. SQL tools? Structured extraction? Different agent patterns?</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47922550">https://news.ycombinator.com/item?id=47922550</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 27 Apr 2026 15:01:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=47922550</link><dc:creator>bimbobruno</dc:creator><comments>https://news.ycombinator.com/item?id=47922550</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47922550</guid></item></channel></rss>