Hello all, I would like to start this discussion regarding if we should list out cascading dependency deletion during schema version change (see sample reference in https://github.com/apache/polaris/pull/5437).
With the sample reference, we will be dropping table polaris_schema.idempotency_records which has index "polaris_schema.idx_idemp_realm_expires" and PK on "idempotency_records_pkey". When we drop the table, it would drop the PK along with index during cascading dependency deletion. One reason to keep those is to easy the revert process if we need to do so. However, keeping all of the dependencies listed out is a bit tedious and add over-head for regular schema upgrade (in this case, instead of running one drop sql, we would need to do 2 drop plus 1 alter table sql statements). Thoughts? Thanks, Yong
