THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Table of contents
Jira Boards
Flink 1.19 Burndown: 1.19 Burndown - Agile Board - ASF JIRA (apache.org)
Sync meeting
- The release sync will start from Nov 14th, 2023, at 9am (CET, UTC+1) and 4pm (UTC+8). The release sync happens bi-weekly at first, and will be adjusted to weekly as we approaching the feature freeze date.
- Feel free to join on Google Meet.
Timeline
- Feature Freeze
- Jan 26, 2024, 00:00 CET(UTC+1)
- Release
- End of Feb 2024
Highlight features
please feel free to add/suggest.
Features
List of features announced by contributors and committers that are likely to be ready for the feature freeze:n
NOTICE: It's preferred if only new features end up there and not all bugs/tasks separately, so that the page is not over bloated. Of course, unless fixing a bug is a really big or important one equivalent to implementing a completely new feature. A good rule of thumb would be that each entry in the page could (but does not have to) be later on included in a release blog post.
Legend
State
| symbol | meaning | comment |
|---|---|---|
 | validated | through cross team testing |
 | done | well documented with a complete test coverage |
 | will make it | there is no reason this effort should not go into 1.19 |
 | in danger | there are some concerns the effort could be ready for the feature freeze of 1.19 |
 | very unlikely | there are severe concerns the effort could make it to 1.19 |
 | won't make it | it was decided against adding this for the 1.19 release. working on the effort has been stopped. |
 | state unclear | |
 | independent | as the artifact could be released independent of Apache Flink |
X-Team verification
| symbol | meaning |
|---|---|
| done |
| not required |
Feature Stage
Please align with the list on the Apache Flink Roadmap (https://flink.apache.org/roadmap.html).
- MVP: Have a look, consider whether this can help you in the future.
- Beta: You can benefit from this, but you should carefully evaluate the feature.
- Ready and Evolving: Ready to use in production, but be aware you may need to make some adjustments to your application and setup in the future, when you upgrade Flink.
- Stable: Unrestricted use in production
- Reaching End-of-Life: Stable, still feel free to use, but think about alternatives. Not a good match for new long-lived projects.
- Deprecated: Start looking for alternatives now
Summary
Numbers are based on the items in the list below, not on the tickets
| | | | | | | | ∑ | Remaining weeks | |
| 2023-11-28 | 2 | 11 | 21 | 10 | ||||||
| 2023-12-12 | 7 | |||||||||
| 2023-12-26 | 5 | |||||||||
| 2024-01-09 | 3 | |||||||||
| 2024-01-23 | 1 |
List
Feel free to add categories.
| Runtime | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Name/JIRA Issue | Responsible Contributor | Reviewer / committer available | Feature Stage | Note | State | % | Updated | Implemented | Documented | X-team verified | Volunteers for testing |
| Shuffle | |||||||||||
| Coordination | |||||||||||
| FLIP-379: Dynamic source parallelism inference for batch jobs | under discussion | 2023-11-14 | |||||||||
| Accepted | | |||||||||
| FLIP-364: Improve the restart-strategy | under discussion | ||||||||||
| FLIP-384: Introduce TraceReporter and use it to create checkpointing and recovery traces | | ||||||||||
| FLIP-385: Add OpenTelemetryTraceReporter and OpenTelemetryMetricReporter | Piotr Nowojski | | |||||||||
| FLIP-383: Support Job Recovery for Batch Jobs | under discussion | 2023-11-14 | |||||||||
| State & Checkpoint | |||||||||||
| |||||||||||
REST | |||||||||||
| Configuration | |||||||||||
FLIP-366: Support standard YAML for FLINK configuration | In development | | 2023-11-14 | ||||||||
| SQL | |||||||||||
| Name/JIRA Issue | Responsible Contributor | Reviewer / committer available | Feature Stage | Note | State | % | Updated | Implemented | Documented | X-team verified | |
| | ||||||||||
| @Yangze Guo | | |||||||||
| FLIP-376: Add DISTRIBUTED BY clause | | ||||||||||
| FLIP-392: Deprecate the Legacy Group Window Aggregation | | ||||||||||
| FLIP-393: Make QueryOperations SQL serializable | | ||||||||||
| Connectors | |||||||||||
| |||||||||||
| |||||||||||
| | ||||||||||
FLIP-371: Provide initialization context for Committer creation in TwoPhaseCommittingSink | Accepted | ||||||||||
| Under discussion | ||||||||||
| Resource Management | |||||||||||
Runtime | |||||||||||
| Rui Fan | RocMarshal | Accepted | | 2023-11-23 | ||||||
A series of optimizations to reduce the memory and cpu usage for large StreamOperator | Rui Fan | | 2023-11-23 | ||||||||
Misc | |||||||||||
| FLIP-375: Built-in cross-platform powerful java profiler | Accepted | | |||||||||
FLINK-33230 Support Expanding ExecutionGraph to StreamGraph in Flink (will create a FLIP) | Under discussion | ||||||||||
Status / Follow-ups
11/14/2023
- Is Google Meet OK for everyone? - ok
- The release sync meeting time, currently Europe has gone into winter time(CET, UTC+1), is 9am ok? - ok
- Daily work divisions
- JIRA ticket (Mainly focus on new blockers, progress of existing blockers each week) lincoln lee
- CI (Failures reported in #build channel and not reported) Martijn Visser
- Benchmark (Check if there's regression in the #flink-dev-benchmarks channel) Yun Tang
- Mailing list monitoring Jing Ge
- This division doesn't mean that other RMs are now allowed to do the work. All RMs should take responsibilities on all of these daily issues if they are available.
- Feature freezing date. - Jan 26, 2024, 00:00 CET(UTC+1)
- Retrospective of 1.18
11/28/2023
- Blockers
- discuss thread
- documentation build failures