<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data-Parsing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/data-parsing/</link>
    <description>Recent content in Data-Parsing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 26 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/data-parsing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Java CSV Libraries in 2026: uniVocity vs Commons CSV vs Jackson CSV — Which Parser Should You Use?</title>
      <link>https://www.pistack.xyz/posts/2026-08-26-java-csv-libraries-univocity-commons-csv-jackson-csv-comparison/</link>
      <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-26-java-csv-libraries-univocity-commons-csv-jackson-csv-comparison/</guid>
      <description>&lt;p&gt;Your Java app will eventually parse a CSV file — it is the universal interchange format for banks, government datasets, e-commerce exports, and pretty much every legacy system still running on mainframes. And that is exactly where naive parsing bites: a 2 GB CSV from a data vendor can turn a 30-second batch job into a 40-minute OOM killer, or silently corrupt rows when a field contains a newline or a quoted comma. The three serious options — &lt;strong&gt;uniVocity parsers, Apache Commons CSV, and Jackson CSV&lt;/strong&gt; — take completely different trade-offs on speed, memory, and API style. This guide compares them with live repository data and real code so you can pick the right one before your next data migration deadline.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
