Hi Dev, There is a Flink compress file benchmark regression discovered when we prepare Flink 2.3 release [1]. It started sometime in Feb after Feb 19th. After some investigation and validation, we believe the regression was introduced by [2] which upgraded lz4-java to 1.10.3 to include CVE fixes (detailed analysis in ticket comments). It was also backported to Flink 2.2 and 2.1 release.
I would like to start a discussion whether we want to have this 10% regression as a blocker for Flink 2.3 release until we find an owner and have it fixed. Thanks, Hao [1] https://issues.apache.org/jira/browse/FLINK-39502 [2] https://github.com/apache/flink/pull/27535
