<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data-Platform on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/data-platform/</link><description>Recent content in Data-Platform on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 23 Sep 2026 15:14:55 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/data-platform/index.xml" rel="self" type="application/rss+xml"/><item><title>Amazon EMR introduces LTS releases starting with Spark 4.1 (emr-spark-8.1.0)</title><link>https://curadevops.metacog.co.kr/insights/2026-09-23-amazon-emr-introduces-long-term-support-with-apache-spark-4/</link><pubDate>Wed, 23 Sep 2026 15:14:55 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-23-amazon-emr-introduces-long-term-support-with-apache-spark-4/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Teams running EMR on EKS should evaluate migrating production Spark workloads to emr-spark-8.1.0 to take advantage of the new 36-month LTS support window, reducing forced upgrade pressure; no hard deadline exists yet.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> EMR LTS changes the upgrade economics for data platform teams — evaluate standardizing on LTS releases to extend support cycles and reduce upgrade toil as part of the next data platform planning cycle.&lt;/li>
&lt;/ul></description></item></channel></rss>