<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hierarchies on Ivan Luminaria</title><link>https://ivanluminaria.com/en/tags/hierarchies/</link><description>Recent content in Hierarchies on Ivan Luminaria</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 20 Jan 2026 08:03:00 +0100</lastBuildDate><atom:link href="https://ivanluminaria.com/en/tags/hierarchies/index.xml" rel="self" type="application/rss+xml"/><item><title>Ragged hierarchies: when the client has no parent and the group has no grandparent</title><link>https://ivanluminaria.com/en/posts/data-warehouse/ragged-hierarchies/</link><pubDate>Tue, 20 Jan 2026 08:03:00 +0100</pubDate><guid>https://ivanluminaria.com/en/posts/data-warehouse/ragged-hierarchies/</guid><description>&lt;p&gt;Three levels. Top Group, Group, Client. It looks like a trivial structure — the kind of hierarchy you draw on a whiteboard in five minutes and that any BI tool should handle without issues.&lt;/p&gt;
&lt;p&gt;Then you discover that not all clients belong to a group. And that not all groups belong to a top group. And that the aggregation reports the business asks for — revenue by top group, client count by group, &lt;span class="glossary-tip" tabindex="0" data-glossary-desc="Navigation in reports from an aggregated level to a detail level, typical of OLAP analysis and data warehouses." data-glossary-url="https://ivanluminaria.com/en/glossary/drill-down/" data-glossary-more="Read more →"&gt;drill-down&lt;/span&gt;
 from the top to the leaf — produce wrong or incomplete results because the hierarchy has holes.&lt;/p&gt;</description></item></channel></rss>