Apache Polaris 1.2.0 introduces significant updates aimed at enhancing control, compatibility, and observability for Iceberg lakehouses. Key features include fine-grained authorization, which allows administrators to set specific permissions for operations like adding snapshots, moving beyond the previous broad permission model. Event persistence is also new, enabling the tracking of catalog activity by saving events in JDBC-compatible databases and AWS CloudWatch, though this feature is still in preview and may evolve in future releases. The update improves role-based access control (RBAC) for federated catalogs, allowing finer access management at the namespace or table level rather than just at the catalog level. This is particularly beneficial for complex environments where teams connect multiple data sources. Additionally, Polaris now supports IAM authentication for Amazon RDS and Aurora PostgreSQL, simplifying security management by eliminating static passwords. Organizations can also connect to S3-compatible storage systems that do not support AWS's Security Token Service, broadening deployment options for Polaris. Several API changes streamline interactions with Polaris, such as returning full objects upon resource creation, which reduces unnecessary API calls. However, there are some breaking changes, including the blocking of custom locations for namespaces by default, which helps maintain catalog integrity. The release also marks the deprecation of certain features, urging users to prepare for future migrations. Overall, these enhancements position Apache Polaris as a robust choice for teams building scalable, flexible lakehouse infrastructures while avoiding vendor lock-in.