The GitHub Actions job "Flink CDC CI" on flink-cdc.git/fix/table-id-router-find-vs-matches has failed. Run started by GitHub user sd4324530 (triggered by lvyanquan).
Head commit for run: 8f99a6837322afbf834947b89bf7a4e2a6f87c50 / Pei Yu <[email protected]> [FLINK-40148][docs] Correct prefix-match compatibility docs per review feedback Follow up to the previous commit based on community review feedback: - Drop the table_17 row whose 3.6.0 result was wrong. The regex '([1-9]|1[0-6])' cannot match 17 via a full match, so calculateRoute() never invokes resolveReplacement() for it, and the source keeps its original id in both 3.6.0 and 3.7.0. 'new_db_6.table_1_suffix7' is only what find()/replaceAll() produce when invoked directly on the regex, not through TableIdRouter.route(). - Broaden the scope beyond multi-character capturing groups: any source-table rule whose regex can both match the full id and match a shorter prefix of the same id triggers the same suffix leak, regardless of capturing groups or $N back-references in the sink template. - Rename the section from 'Multi-Character Capturing Groups' to 'Sink-Table Suffix Leak from Prefix Matches' (EN) / '前缀匹配导致的 Sink-Table 后缀泄漏' (ZH) to better describe the actual condition, and remove Java API references (Matcher.matches / Matcher.find) from the prose in favor of plain language. Signed-off-by: Pei Yu <[email protected]> Report URL: https://github.com/apache/flink-cdc/actions/runs/35608362593 With regards, GitHub Actions via GitBox
