This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Page tree
Skip to end of metadata
Go to start of metadata

This page describes a proposed Flink Improvement Proposal (FLIP) process for proposing a major change to Flink.

To create your own FLIP, click on "Create" on the header and choose "FLIP-Template" other than "Blank page".


The purpose of FLIPs is to have a central place to collect and document planned major enhancements to Apache Flink. While JIRA is still the tool to track tasks, bugs, and progress, the FLIPs give an accessible high level overview of the result of design discussions and proposals. Think of FLIPs as collections of major design documents for user-relevant changes.

We want to make Flink a core architectural component for users. We also support a large number of integrations with other tools, systems, and clients. Keeping this kind of usage healthy requires a high level of compatibility between releases — core architectural elements can't break compatibility or shift functionality from release to release. As a result each new major feature or public API has to be done in a way that we can stick with it going forward.

This means when making this kind of change we need to think through what we are doing as best we can prior to release. And as we go forward we need to stick to our decisions as much as possible. All technical decisions have pros and cons so it is important we capture the thought process that lead to a decision or design to avoid flip-flopping needlessly.

Hopefully we can make these proportional in effort to their magnitude — small changes should just need a couple brief paragraphs, whereas large changes need detailed design discussions.

This process also isn't meant to discourage incompatible changes — proposing an incompatible change is totally legitimate. Sometimes we will have made a mistake and the best path forward is a clean break that cleans things up and gives us a good foundation going forward. Rather this is intended to avoid accidentally introducing half thought-out interfaces and protocols that cause needless heartburn when changed. Likewise the definition of "compatible" is itself squishy: small details like which errors are thrown when are clearly part of the contract but may need to change in some circumstances, likewise performance isn't part of the public contract but dramatic changes may break use cases. So we just need to use good judgement about how big the impact of an incompatibility will be and how big the payoff is.

What is considered a "major change" that needs a FLIP?

Any of the following should be considered a major change:

  • Any major new feature, subsystem, or piece of functionality
  • Any change that impacts the public interfaces of the project

What are the "public interfaces" of the project?

All of the following are public interfaces that people build around:

  • DataStream and DataSet API, including classes related to that, such as StreamExecutionEnvironment
  • Classes marked with the @Public annotation
  • On-disk binary formats, such as checkpoints/savepoints
  • User-facing scripts/command-line tools, i.e. bin/flink, Yarn scripts, Mesos scripts
  • Configuration settings
  • Exposed monitoring information

Not all compatibility commitments are the same. We need to spend significantly more time on public APIs as these can break code for users. They cause people to rebuild code and lead to compatibility issues in large multi-dependency projects (which end up requiring multiple incompatible versions). Configuration, monitoring, and command line tools can be faster and looser — changes here will break monitoring dashboards and require a bit of care during upgrades but aren't a huge burden.

For the most part monitoring, command line tool changes, and configs are added with new features so these can be done with a single FLIP.

What should be included in a FLIP?

A FLIP should contain the following sections:

  • Motivation: describe the problem to be solved
  • Proposed Change: describe the new thing you want to do. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences, depending on the scope of the change.
  • New or Changed Public Interfaces: impact to any of the "compatibility commitments" described above. We want to call these out in particular so everyone thinks about them.
  • Migration Plan and Compatibility: if this feature requires additional support for a no-downtime upgrade describe how that will work
  • Rejected Alternatives: What are the other alternatives you considered and why are they worse? The goal of this section is to help people understand why this is the best solution now, and also to prevent churn in the future when old alternatives are reconsidered.

Who should initiate the FLIP?

Anyone can initiate a FLIP but you shouldn't do it unless you have an intention of getting the work done to implement it (otherwise it is silly).


Here is the process for making a FLIP:

  1. Create a page which is a child of this one. Take the next available FLIP number and give your proposal a descriptive heading. e.g. "FLIP 42: Enable Flink Streaming Jobs to stop gracefully". If you don't have the necessary permissions for creating a new page, please ask on the development mailing list.
  2. Fill in the sections as described above
  3. Start a [DISCUSS] thread on the Apache mailing list. Please ensure that the subject of the thread is of the format [DISCUSS] FLIP-{your FLIP number} {your FLIP heading} The discussion should happen on the mailing list not on the wiki since the wiki comment system doesn't work well for larger discussions. In the process of the discussion you may update the proposal. You should let people know the changes you are making.
  4. Once the proposal is finalized call a [VOTE] to have the proposal adopted. These proposals are more serious than code changes and more serious even than release votes. The criteria for acceptance is consensus.
  5. Please update the FLIP wiki page, and the index below, to reflect the current stage of the FLIP after a vote. This acts as the permanent record indicating the result of the FLIP (e.g., Accepted or Rejected). Also report the result of the FLIP vote to the voting thread on the mailing list so the conclusion is clear.

FLIP round-up

Next FLIP Number: 73

Use this number as the identifier for your FLIP and increment this value.

Adopted/Accepted but unreleased FLIPs

FLIPTarget ReleaseLink to Discussion Thread
FLIP-16: Loop Fault ToleranceTBD
FLIP-17 Side Inputs for DataStream APITBD
FLIP-23: Model Serving  TBD
FLIP-30: Unified Catalog APIsTBD
FLIP-32: Restructure flink-table for future contributionsTBD

FLIP-35: Support Chinese Documents and Website

FLIP-37: Rework of the Table API Type System1.10

FLIP-39: Flink ML pipeline and ML libs

FLIP-41: Unify Canonical Binary Format for Keyed StateTBD
FLIP-43: State Processing API1.9

FLIP-49: Unified Memory Configuration for TaskExecutors1.10
FLIP-50: Spill-able Heap Keyed State Backend1.10
FLIP-51: Rework of the Expression Design1.10
FLIP-52: Remove legacy Program interface.1.10
FLIP-53: Fine Grained Operator Resource Management1.10

FLIP-58: Flink Python User-Defined Stateless Function for Table


FLIPs under discussion

FLIPStateLink to Discussion Thread
FLIP-5: Only send data to each taskmanager once for broadcastsDiscuss
FLIP-14: crossGroup OperatorDiscuss
FLIP-15: Redesign Iterations (Scoping, Flow Control and Termination)Discuss
FLIP-18: Code Generation for improving sorting performanceDiscuss
FLIP-21: Improve object Copying for Streaming RuntimeDiscuss
FLIP-22: Eager State DeclarationDiscuss
FLIP-26: Service AuthorizationDiscuss
FLIP-27: Refactor Source InterfaceDiscuss

FLIP-33: Standardize Connector Metrics

FLIP-36: Support Interactive Programming in FlinkDiscuss
FLIP-40: Flink DriverDiscuss
FLIP-44: Support Local Aggregation in FlinkDiscuss
FLIP-45: Reinforce Job Stop SemanticDiscuss
FLIP-46: Graceful Shutdown Handling by UDFsDiscuss
FLIP-47: Checkpoints vs. SavepointsDiscuss
FLIP-54: Evolve ConfigOption and ConfigurationDiscuss
FLIP-55: Introduction of a Table API Java Expression DSLDiscuss
FLIP-56: Dynamic Slot AllocationDiscuss
FLIP-59: Enable execution configuration from Configuration objectDiscuss
FLIP-60: Restructure the Table API & SQL documentationDiscuss
FLIP-64: Support for Temporary Objects in Table moduleDiscuss
FLIP-66: Support time attribute in SQL DDLDiscuss
FLIP-67: Global partitions lifecycleDiscuss

FLIP 69 - Flink SQL DDL EnhancementDiscuss
FLIP-72: Introduce Pulsar ConnectorDiscuss

Implemented and Released FLIPs

FLIPFirst Release VersionLink to Discussion Thread
FLIP-1: Fine Grained Recovery from Task Failures1.9
FLIP-2: Extending Window Function Metadata1.3
FLIP-3: Improving Organization of Documentation1.2
FLIP-4: Enhance Window Evictor1.2

FLIP-7: Expose metrics to WebInterface1.2
FLIP-8: Rescalable Non-Partitioned State1.2

FLIP-10: Unify Checkpoints and Savepoints1.2

FLIP-11: Table API Stream Aggregations

FLIP-12: Asynchronous I/O Design and Implementation1.2
FLIP-13: SideOutputs in Flink1.3

FLIP-19: Improved BLOB storage architecture

FLIP-20: Integration of SQL and CEP1.7

FLIP-24: SQL Client1.5
FLIP-25: TTL for State1.6

FLIP-29: Support map/flatMap/aggregate/flatAggregate on TableAPI

FLIP-31: Pluggable Shuffle Manager1.9
FLIP-34: Terminate/Suspend Job with Savepoint1.9
FLIP-38: Python Table API1.9
FLIP-61: Simplify Flink's cluster level RestartStrategy configuration1.10
FLIP-62: Set default restart delay for FixedDelay- and FailureRateRestartStrategy to 1s1.10

Discarded FLIPs

FLIP-9: Trigger DSLDecided to not work on that, at least at the moment.

FLIP-28: Long-term goal of making flink-table Scala-free

This FLIP is part of the bigger vision described in FLIP-32.
  • No labels