yuqi1129 opened a new issue, #14729:
URL: https://github.com/apache/gravitino/issues/14729
### Version
main branch
### Describe what's wrong
When reading Doris 1.2 table metadata, MySQL JDBC metadata can expose a
native LARGEINT column as INT. Gravitino consequently reports integer instead
of ExternalType("largeint"). A LARGEINT default outside the INT range also
causes table loading to fail.
### Error message and/or stacktrace
NumberFormatException: For input string:
"170141183460469231731687303715884105727"
### How to reproduce
1. Use a Doris catalog backed by Doris 1.2.
2. Create a Doris table with an INT key and a LARGEINT value column whose
default is '170141183460469231731687303715884105727'.
3. Load the table through Gravitino. Without the default, the LARGEINT
column can be reported as integer; with this default, loading fails.
### Additional context
Doris information_schema.COLUMNS preserves the native type in COLUMN_TYPE.
The fix should use this declaration without changing ordinary INT or BIGINT
mappings.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
