Hi Xingcan,
in theory there should be no hard blocker for supporting this. The
implementation should be flexible enough at most locations. We just
adopted 38 from the Blink code base which adopted it from Hive.
However, this could be a breaking change for existing pipelines and we
would need to offer a flag to bring back the old behavior. It would
definitely lead to a lot of testing work to not cause inconsistencies.
Do you think this is a hard blocker for users?
Regards,
Timo
On 28.08.21 00:21, Xingcan Cui wrote:
Hi all,
Recently, I was trying to load some CDC data from Oracle/Postgres databases
and found that the current precision range [1, 38] for DecimalType may not
meet the requirement for some source types. For instance, in Oracle, if a
column is declared as `NUMBER` without precision and scale, the values in
it could potentially be very large. As DecimalType is backed by Java
BigDecimal, I wonder if we should extend the precision range.
Best,
Xingcan
