Amazon EMR now supports Apache Spark 4.0.2 across all three deployment models. With Spark 4.0.2, you can build and maintain data pipelines more easily with ANSI SQL and VARIANT data types, enforce fine-grained access control (FGAC) at the row level or column level, strengthen compliance and governance frameworks with Apache Iceberg v3 table format, and deploy new real-time applications faster with enhanced streaming capabilities.
With Spark 4.0.2, you can build data pipelines, making data engineering accessible to a broader range of users through standard ANSI SQL support, eliminating the need to learn Spark-specific syntax. Spark 4.0.2 natively supports JSON and semi-structured data through VARIANT data types, providing flexibility for handling diverse data formats. You can enforce fine-grained access control (FGAC) on both read and write operations for AWS Lake Formation registered tables in your Apache Spark jobs. Building on these security capabilities, Apache Iceberg v3 table format provides stronger transaction guarantees and tracks data lineage, creating the audit trails required for regulatory compliance. Enhanced streaming controls simplify management of complex stateful operations and improve monitoring, enabling you to deploy real-time applications for fraud detection, personalization, and other time-sensitive use cases faster.
Apache Spark 4.0.2 is available in all regions where EMR is available. If you are upgrading your existing EMR application, you can use Apache Spark upgrade agent to accelerate your upgrades. To learn more about Apache Spark 4.0.2 on Amazon EMR, visit the Amazon EMR release notes, or get started by creating an EMR application with Spark 4.0.2 from the AWS Management Console.
Categories: general:products/amazon-emr,marketing:marchitecture/analytics
Source: Amazon Web Services
Latest Posts
- Amazon EMR now supports Apache Spark 4.0.2 in general availability

- Power Platform admin center – Discover what’s driving engagement with the Usage page [MC1310378]
![Power Platform admin center - Discover what's driving engagement with the Usage page [MC1310378] 3 pexels david bares 42311 424436](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- [Action Required] Update scripts using Get-MailDetailTransportRuleReport and Get-MailTrafficPolicyReport [MC1323250]
![[Action Required] Update scripts using Get-MailDetailTransportRuleReport and Get-MailTrafficPolicyReport [MC1323250] 4 pexels earano 3608311](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- Amazon SageMaker HyperPod Slurm clusters now support specifying minimum capacity requirements with continuous provisioning



![Power Platform admin center - Discover what's driving engagement with the Usage page [MC1310378] 3 pexels david bares 42311 424436](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-david-bares-42311-424436-150x150.webp)
![[Action Required] Update scripts using Get-MailDetailTransportRuleReport and Get-MailTrafficPolicyReport [MC1323250] 4 pexels earano 3608311](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-earano-3608311-150x150.webp)
