lasdf1234 opened a new issue, #12998:
URL: https://github.com/apache/gravitino/issues/12998
### Version
main branch
### Describe what's wrong
Several catalog connectors catch precise errors from the underlying system
and replace them with a generic message that only names the operation/object.
The upstream text is kept only in the stack trace, which the UI does not show,
so operators cannot act on the failure.
Examples:
- **Kafka:** invalid topic config returns `Failed to alter topic
properties...` (often 500) instead of Kafka's `InvalidConfigurationException`
detailing allowed values (should be 400).
- **Glue:** failures become `Glue error: <object>`; IAM
`AccessDeniedException` details are dropped (should surface as 403 where
appropriate).
The same wrap-without-cause-message pattern also appears in Hive/HMS,
Fileset, Model, Lance, and related paths.
### Error message and/or stacktrace
Kafka example:
```
500 {"code":1002,"type":"RuntimeException",
"message":"... reason [Failed to alter topic properties for topic
prop_probe]"}
Caused by: org.apache.kafka.common.errors.InvalidConfigurationException:
Invalid value nonsense for configuration cleanup.policy: String must be
one of: compact, delete
```
### How to reproduce
1. Use a Kafka catalog and `PUT` a topic property such as
`cleanup.policy=nonsense`.
2. Observe that the API response message lacks Kafka's validation text and
the status is 500.
### Additional context
Related enterprise report: datastrato/gravitino-enterprise#1803 (DAT-877).
Oracle/SQL Server comment cases are filed separately and out of scope for this
fix.
--
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]
