Hi Celeborn Community, I wanted to get an opinion about merging SystemConfigs table (`celeborn_cluster_system_config`) and TenantConfig table (`celeborn_cluster_tenant_config`) for DB config service. As they essentially represent similar data with some additional metadata like level, tenant_id and name. We can use the same schema as of `celeborn_cluster_tenant_config` for the new table and for SystemConfigs – `level` can be defined as `SYSTEM`. tenant_id and user can be '' (empty string).
Pros: - Config's precedence can be seen by a single query. Currently users will have to check both tables for a config override. - Less number of DB queries while refreshing cache. - All the configs will be present on the same table providing ease of maintaining only a single table and will reduce code around it. Thanks Sanskar Modi
