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
wrote:
> I think th
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 wrote:
> Hi all,
>
> Currently, we can *enforce default table properties* at catalog level
> with configs like
> spark.sql.catalog.*catalog-name*.table-ove
