diqiu50 opened a new issue, #14873:
URL: https://github.com/apache/gravitino/issues/14873
### Version
main branch
### Describe what's wrong
Two column checks of the Glue catalog do not match the table format:
1. `GlueCatalogCapability.columnNotNull()` is unsupported for the whole
catalog, so NOT NULL columns are refused on Iceberg tables too, both on create
and on `updateColumnNullability`. Iceberg tables keep nullability in their
metadata, and the docs list column nullability updates as supported for Iceberg
tables.
2. Hive-format tables accept `char` and `varchar` lengths outside the Hive
limits (`char` 1 to 255, `varchar` 1 to 65535). Glue stores the type string as
is, so the table is created, but Hive-based readers fail to parse the type.
### Error message and/or stacktrace
```
AWS Glue Data Catalog does not support NOT NULL constraints on columns.
Illegal column: name
```
### How to reproduce
1. Create an Iceberg table in a Glue catalog, then alter it with
`{"@type":"updateColumnNullability","fieldName":["name"],"nullable":true}`. It
returns HTTP 400.
2. Create a Hive-format table with a column of type `char(256)` or
`varchar(0)`. It returns HTTP 200.
--
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]