# Flarion blog: the hard part of a Spark upgrade is proving the output did not change

News, 18 Aug 2026

**The short answer.** Flarion published a blog post on August 18, 2026 arguing that validation, not code rewriting, is the main obstacle to Spark version upgrades. It cites Slack's Spark 2 to 3 move across 60+ EMR clusters and 40+ teams, and Uber's 2.4 to 3.3 upgrade with over two million applications daily.

Flarion's blog post of August 18, 2026, by Ran Reichman, responds to the AWS Spark Upgrade Agent, which it says rewrites Spark jobs for Spark 4.0. Flarion's argument is that the code rewrite is not the main impediment to upgrading enterprise Spark workloads.

The post says Slack's Spark 2 to 3 migration took about a year across 60+ EMR clusters and 40+ teams, with exact-match checks for billing pipelines. It says Uber moved from Spark 2.4 to 3.3 with over two million Spark applications running daily, using a shadow-testing framework to compare outputs before marking a job migrated. These are Flarion's reading of those companies' write-ups.

Flarion sells a Spark plugin, so the post sits next to its product pitch. A team weighing an upgrade or a plugin can use the same question for both: how would the output be compared before and after.

## Sources

- Flarion blog: The Hard Part of Upgrading Spark Versions Isn't the Code: https://www.flarion.io/blog/the-hard-part-of-upgrading-spark-versions-isnt-the-code (read 10 Nov 2026)
- Flarion blog: https://www.flarion.io/blog (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://sparkaccelerationcompare.com/news/flarion-spark-upgrade-validation/
