You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "nsivabalan (via GitHub)" <gi...@apache.org> on 2026/06/25 03:21:36 UTC
Re: [I] failed to delete from an empty table again [hudi]
nsivabalan commented on issue #16026:
URL: https://github.com/apache/hudi/issues/16026#issuecomment-4795519508
This appears to be fixed on current master by [PR #18030](https://github.com/apache/hudi/pull/18030) (commit `21eb05e7`), which rewrote `BaseHoodieWriteClient.setWriteSchemaForDeletes` to use `TableSchemaResolver.getTableSchemaIfPresent(false)` instead of reading the latest commit metadata directly. The resolver has a fallback chain that tries `tableConfig.getTableCreateSchema()` when commit metadata has no schema, and since Spark SQL `CREATE TABLE` already persists `CREATE_SCHEMA` in table config (`HoodieCatalogTable.scala:235`), the second `DELETE FROM ... WHERE 1!=1` should now succeed instead of throwing `Latest commit does not have any schema in commit metadata`. Could you verify on a current build and close the issue / HUDI-6378 if confirmed?
--
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-unsubscribe@hudi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org