Code Style and Quality Guide — Common Rules # Preamble # Pull Requests & Changes # Common Coding Guide # Java Language Guide # Scala Language Guide # Components Guide # Formatting Guide # 1. Copyright # Each file must include the Apache license information as a header. /* * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements.| flink.apache.org
Code Style and Quality Guide — Components Guide # Preamble # Pull Requests & Changes # Common Coding Guide # Java Language Guide # Scala Language Guide # Components Guide # Formatting Guide # Component Specific Guidelines # Additional guidelines about changes in specific components. Configuration Changes # Where should the config option go? ‘flink-conf.yaml’: All configuration that pertains to execution behavior that one may want to standardize across jobs.| flink.apache.org
Code Style and Quality Guide — Java # Preamble # Pull Requests & Changes # Common Coding Guide # Java Language Guide # Scala Language Guide # Components Guide # Formatting Guide # Java Language Features and Libraries # Preconditions and Log Statements # Never concatenate strings in the parameters Don’t: Preconditions.checkState(value <= threshold, "value must be below " + threshold) Don’t: LOG.| flink.apache.org
Code Style and Quality Guide — Pull Requests & Changes # Preamble # Pull Requests & Changes # Common Coding Guide # Java Language Guide # Scala Language Guide # Components Guide # Formatting Guide # Rationale: We ask contributors to put in a little bit of extra effort to bring pull requests into a state that they can be more easily and more thoroughly reviewed. This helps the community in many ways:| flink.apache.org
Code Style and Quality Guide — Scala # Preamble # Pull Requests & Changes # Common Coding Guide # Java Language Guide # Scala Language Guide # Components Guide # Formatting Guide # Scala Language Features # Where to use (and not use) Scala # We use Scala for Scala APIs or pure Scala Libraries. We do not use Scala in the core APIs and runtime components.| flink.apache.org
Apache Flink Code Style and Quality Guide # Preamble # Pull Requests & Changes # Common Coding Guide # Java Language Guide # Scala Language Guide # Components Guide # Formatting Guide # This is an attempt to capture the code and quality standard that we want to maintain. A code contribution (or any piece of code) can be evaluated in various ways: One set of properties is whether the code is correct and efficient.| flink.apache.org