[
https://issues.apache.org/jira/browse/FLINK-39758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yanquan Lv resolved FLINK-39758.
--------------------------------
Fix Version/s: cdc-3.7.0
Resolution: Fixed
Merged in master via 7355d76c132e19e7ddb9af25dd79a178ce53f1ff.
> Fix DECIMAL OOB in SchemaMergingUtils
> -------------------------------------
>
> Key: FLINK-39758
> URL: https://issues.apache.org/jira/browse/FLINK-39758
> Project: Flink
> Issue Type: Bug
> Components: Flink CDC
> Reporter: Mao Jiayi
> Assignee: Mao Jiayi
> Priority: Major
> Labels: pull-request-available
> Fix For: cdc-3.7.0
>
>
> When merging DECIMAL types from multiple tables in a route-merge pipeline,
> the job may fail if the computed result precision exceeds the maximum allowed
> value.
> The failure happens in *SchemaMergingUtils.mergeDecimalTypes()* and
> {*}SchemaUtils.inferWiderType(){*}. The current implementation calculates the
> merged precision as {{{}max(lhsIntDigits, rhsIntDigits) + max(lhsScale,
> rhsScale){}}}, and then uses *Preconditions.checkArgument* to enforce that
> this value must not exceed {*}DecimalType.MAX_PRECISION (38){*}. When the sum
> exceeds 38, an *IllegalArgumentException* is thrown and the entire pipeline
> fails.
> This issue is typically exposed in multi-table route-merge scenarios where
> tables from different data sources have DECIMAL columns with significantly
> different precisions and scales.
> This issue is not specific to any particular source connector. It can affect
> any pipeline that uses route-merge to combine tables with mismatched DECIMAL
> precisions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
