<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data on BXM.net</title>
    <link>https://bxm.net/tags/data/</link>
    <description>Recent content in Data on BXM.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 22 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bxm.net/tags/data/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hashing 100,000 JSON Lines Found No Duplicates, Hashing Them With Canon Found 9,900</title>
      <link>https://bxm.net/hashing-100000-json-lines-found-no-duplicates-hashing-them-with-canon-found-9900/</link>
      <pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bxm.net/hashing-100000-json-lines-found-no-duplicates-hashing-them-with-canon-found-9900/</guid>
      <description>&lt;p&gt;Event pipelines get the same event twice. A producer times out, retries, and the retry goes through a different service that writes JSON its own way. The usual dedupe is a hash of each line, and it quietly misses all of these.&lt;/p&gt;&#xA;&lt;p&gt;We generated a stream of 100,000 JSON lines from a fixed seed, 13.1 MB in all. 90,000 are distinct purchase events. The other 10,000 are resends of earlier events, written by two other producers. One sorts the keys and escapes non-ASCII, so &amp;ldquo;Zürich&amp;rdquo; arrives as &lt;code&gt;Z\u00fcrich&lt;/code&gt;. The other reverses the key order and adds spaces. For a twist, 100 of the resends come from a producer that writes the quantity as a float: &lt;code&gt;2.0&lt;/code&gt; where the original said &lt;code&gt;2&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
