fpierrick opened a new issue, #6380: URL: https://github.com/apache/gravitino/issues/6380
### Version main branch ### Describe what's wrong Hi folks, I see in my gravitino logs that it tries to purge some meta data from my gravitino backend which uses PostgreSQL 14.8. But it uses the LIMIT clause directly in the DELETE statement which is not supported by postgresql. ### Error message and/or stacktrace [PSQLExceptionLimit.log](https://github.com/user-attachments/files/18574349/PSQLExceptionLimit.log) ### How to reproduce Gravitino : 0.7.0-incubating Postgresql for the gravitino backend. Version 14.8 in my case but all versions should be KO. # THE CONFIGURATION FOR Gravitino ENTITY STORE # The entity store to use, we only supports relational gravitino.entity.store = relational # The backend for the entity store, we only supports JDBC gravitino.entity.store.relational = JDBCBackend # The JDBC URL for the entity store gravitino.entity.store.relational.jdbcUrl = jdbc:postgresql://localhost:5432/gravitino_metalake?currentSchema=gravitino_schema # The JDBC driver class name gravitino.entity.store.relational.jdbcDriver = org.postgresql.Driver # The JDBC user name gravitino.entity.store.relational.jdbcUser = gravitino # The JDBC password gravitino.entity.store.relational.jdbcPassword = XXXXX In gravitino logs, you can see the ERROR when the purge is executed. Maybe you should create and delete a catalog with at least one table. ### Additional context _No response_ -- 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: commits-unsubscr...@gravitino.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
