diqiu50 opened a new issue, #13010: URL: https://github.com/apache/gravitino/issues/13010
### Version main branch ### Describe what's wrong AWS Glue keeps views and tables in the same namespace, storing a view as an object with `TableType: VIRTUAL_VIEW`. The Glue catalog never inspects `Table.tableType()`, so a view is listed and loaded as an ordinary table, and can be deleted through the table API. ### Error message and/or stacktrace No error is raised — the view is returned as a successful table response, which is the problem. ### How to reproduce 1. Create a view in a Glue database, e.g. through Athena: `CREATE VIEW db.v AS SELECT * FROM db.t`. 2. Create a Gravitino catalog with the `glue` provider pointing at that Glue catalog. 3. `GET .../schemas/db/tables` lists the view; `GET .../tables/v` returns 200 with columns. Observed on 1.3.0. ### Additional context Representing Glue views as views, so that the view definition is not discarded, will be tracked separately. -- 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]
