snuyanzin commented on code in PR #832:
URL: https://github.com/apache/flink-web/pull/832#discussion_r2916288905


##########
docs/content/posts/2026-03-01-community-update.md:
##########
@@ -0,0 +1,148 @@
+---
+authors:
+- davidrad: null
+  name: David Radley
+date: "2026-03-01T08:00:00Z"
+excerpt: Flink Community update for March 2026
+title: Flink Community update for March 2026
+aliases:
+- /news/2026/03/01/community-update.html
+---
+
+<!-- TOC -->
+  * [Developer/Technical Updates](#developertechnical-updates)
+    * [Key Themes](#key-themes)
+    * [What happened last month](#what-happened-last-month)
+  * [User-Facing Updates](#user-facing-updates)
+    * [Kubernetes Operator 1.14.0 Release](#kubernetes-operator-1140-release)
+    * [Apache Flink Connector Parent 2.0.0 
Release](#apache-flink-connector-parent-200-release)
+    * [Apache Flink Connector AWS 6.0 
Release](#apache-flink-connector-aws-60-release)
+    * [Apache Flink Agents 0.2.0 released](#apache-flink-agents-020-released)
+    * [Blogs](#blogs)
+  * [Governance and Community](#governance-and-community)
+    * [FLIP Activity](#flip-activity)
+      * [Accepted - being implemented](#accepted---being-implemented)
+      * [Being discussed](#being-discussed)
+    * [Apache Flink Dev List activity](#apache-flink-dev-list-activity)
+  * [For more information](#for-more-information)
+<!-- TOC -->
+
+Previous Blog: [Flink community update February 
2026](https://flink.apache.org/2026/02/01/flink-community-update-february26/)
+
+A strong February; there was a lot of commit activity with 320 open PRs in the 
main repository (600+ across all Flink projects) and 4 new releases.
+
+## Developer/Technical Updates
+
+### Key Themes
+
+1. Additional Serviceability
+   - [[FLINK-38977] Expose exceptions for 
applications](https://issues.apache.org/jira/browse/FLINK-38977)
+   - [[hotfix] Log watermark alignment duration (and all other 
stages)](https://github.com/apache/flink/commit/f6fffd7d33f617acc69f405deecf050ef710d439)
+   - [[hotfix] Log unexpected non-terminal task 
state](https://github.com/apache/flink/commit/79e79fcd26eeaabb956198ce2c6293cc221a9f5e)
+2. Improvements to watermarks
+   - [[FLINK-37399] Buffer watermarks for watermark 
alignment](https://issues.apache.org/jira/browse/FLINK-37399)
+   - [[FLINK-37399] Add 
SamplingWatermarkRingBuffer](https://issues.apache.org/jira/browse/FLINK-37399)
+   - [[FLINK-39167] Initialize source output before emitting final 
watermark](https://issues.apache.org/jira/browse/FLINK-39167)
+3. Improved recovery with checkpoints
+   - [[hotfix] Try to get last checkpoint on recovery regardless of 
checkpointing 
interval](https://github.com/apache/flink/commit/c0ada39aafa23e58e6c80883bdb740a89d02c1ff)
+   - [[hotfix] Move checkpointing configuration code to 
CheckpointCoordinatorConfiguration](https://github.com/apache/flink/commit/b2b044dc66814498f0cdfb4e9249f446e2c6fce9)
+   - [[FLINK-38939] Pause Sources until the first checkpoint barrier is 
received](https://issues.apache.org/jira/browse/FLINK-38939)
+4. Enhancements around splits
+   - [[FLINK-39073] Improve logging of invalid split 
transitions](https://issues.apache.org/jira/browse/FLINK-39073)
+   - [[FLINK-39073] Defer alignment check for idle 
splits](https://issues.apache.org/jira/browse/FLINK-39073)
+5. Table planner enhancements
+   - [[FLINK-37924] Introduce Built-in Function to Access field or element in 
the Variant](https://issues.apache.org/jira/browse/FLINK-37924)
+   - [[FLINK-35661] Fix MiniBatchGroupAggFunction silently dropping 
records](https://issues.apache.org/jira/browse/FLINK-35661)
+   - [[FLINK-38913] ArrayIndexOutOfBoundsException while unparsing 
ExtendedSqlRowTypeNameSpec](https://issues.apache.org/jira/browse/FLINK-38913)

Review Comment:
   to be more precise this is not a planner change, rather parser



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to