Hi all, I’d like to propose using Lombok[1] in the Flink codebase beyond tests. Flink already uses Lombok 1.18.42 in flink-core tests [2], but not beyond that. There are many places where Lombok can be useful and avoid repetitive code across the codebase. For example, the native S3 module has a few simple value classes, such as S3BlockLocation[3], S3BucketConfig[4], and others, where Lombok could remove repetitive constructors and getters.
Bests, Samrat [1] https://projectlombok.org/ [2] https://github.com/apache/flink/blob/2b9453a6d11d091e8a734e1fc0b0abc49e45628a/flink-core/pom.xml#L177 [3] https://github.com/apache/flink/blob/2b9453a6d11d091e8a734e1fc0b0abc49e45628a/flink-filesystems/flink-s3-fs-native/src/main/java/org/apache/flink/fs/s3native/S3BucketConfig.java#L39 [4] https://github.com/apache/flink/blob/2b9453a6d11d091e8a734e1fc0b0abc49e45628a/flink-filesystems/flink-s3-fs-native/src/main/java/org/apache/flink/fs/s3native/S3BlockLocation.java#L25
