sundapeng commented on PR #8728: URL: https://github.com/apache/paimon/pull/8728#issuecomment-5015587721
Pushed an update that slims the first version down (−868 lines in this PR, −2.7k across the stack), dropping speculative fallback machinery while keeping all data-safety semantics: - Removed the ALTER-time client-side validation machinery and the catalog-default discard logic. Non-REST catalogs keep their previous behavior (the option stays inert); the REST catalog validates the managed combination at `CREATE TABLE` with `table-default.*` participating. Any table carrying an unhonorable option loads as unmanaged with a WARN and can be repaired via `ALTER TABLE ... UNSET` — the load-time downgrade is the single safety net. - Collapsed the provider's dual (uuid + name) generation tracking into one name-keyed generation; listings live in per-instance caches, so a shared counter can only over-invalidate, never serve stale data. - Dropped defensive null-page checks and the `CREATE TABLE IF NOT EXISTS` replay special case. The follow-up PRs #8729/#8730 were slimmed accordingly (no server prefix pushdown for DROP expansion; sync procedure surface reduced to `table/mode/dry_run`; filtered listing uses verbatim catalog tokens with sparse pages). Also, the previous `build_test` failure was `CoordinatorCommitITCase.testCoordinatorCommitMetricsAndCommittedRows` (NPE while polling writer metrics in paimon-flink-common) — unrelated to this PR, which touches no Flink code; the new push re-runs CI. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
