Stop per-boot customer_id FK tug-of-war in SchemaCleanupRunner

PerformanceInitializerService
Ya
26 Juni 2026, 21:17 UTC
Mwandishi
Kamo
Ahadi ya
eea4c16

Remove the stale RetailCustomer->Account cleanup drops of commerce_carts.customer_id, **************** and **************** Those columns are now live, Hibernate-owned FK columns (Cart.customer / DraftOrder.customer map @JoinColumn(name="customer_id") -> accounts), so ddl-auto:update re-added the column and re-validated the FK to accounts (~7 min on this cluster) on EVERY startup only for this runner to drop it again. That tug-of-war was ~7 of the ~11 min runtime and left the columns absent at rest. Letting Hibernate own them builds the FK once and it persists; steady-state init should drop toward ~3-4 min.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei