Manu, this is something that you can easily build into a REST catalog implementation. I think that's probably the best way to solve it, rather than trying to implement this behavior across all of the catalogs in the project, right?
On Wed, Nov 27, 2024 at 8:47 AM Pucheng Yang <py...@pinterest.com.invalid> wrote: > I think the naming of the property should be fixed as it only applies for > any new table creation. > > On Wed, Nov 27, 2024 at 2:21 AM Manu Zhang <owenzhang1...@gmail.com> > wrote: > >> Hi all, >> >> Currently, we can *enforce default table properties* at catalog level >> with configs like >> spark.sql.catalog.*catalog-name*.table-override.*propertyKey*[1]. It >> prevents users from overriding those properties when creating a table. >> However, users can still override later through altering the table. >> The Spark doc is inconsistent saying that the table-override property >> can't be overridden by user. Which one is expected? >> >> >> 1. >> https://iceberg.apache.org/docs/nightly/spark-configuration/#catalog-configuration >> <https://iceberg.apache.org/docs/nightly/spark-configuration/#catalog-configuration> >> >> >> Thanks, >> Manu >> >
