[
https://issues.apache.org/jira/browse/HUDI-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Zhang updated HUDI-7297:
----------------------------
Description:
If you create a table with mismatched file types in Flink SQL, for example you
define a field as bigint while the actual field type is int, an
IllegalArgumentException would be thrown like below:
java.lang.IllegalArgumentException: Unexpected type: INT32
The exception is way too ambiguous. It is difficult to figure out which field
type is incorrect and what the correct type is. You have to refer to the source
code.
Currently I plan to make the exception message more informative.
was:
If you create a table with mismatched file types, for example you define a
field as bigint while the actual field type is int, an IllegalArgumentException
would be thrown like below:
java.lang.IllegalArgumentException: Unexpected type: INT32
The exception is way too ambiguous. It is difficult to figure out which field
type is incorrect and what the correct type is. You have to refer to the source
code.
Currently I plan to make the exception message more informative.
> Exception thrown when field type mismatch is ambiguous
> ------------------------------------------------------
>
> Key: HUDI-7297
> URL: https://issues.apache.org/jira/browse/HUDI-7297
> Project: Apache Hudi
> Issue Type: Improvement
> Reporter: Yao Zhang
> Assignee: Yao Zhang
> Priority: Minor
>
> If you create a table with mismatched file types in Flink SQL, for example
> you define a field as bigint while the actual field type is int, an
> IllegalArgumentException would be thrown like below:
> java.lang.IllegalArgumentException: Unexpected type: INT32
> The exception is way too ambiguous. It is difficult to figure out which field
> type is incorrect and what the correct type is. You have to refer to the
> source code.
> Currently I plan to make the exception message more informative.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
