JNSimba opened a new pull request, #63514: URL: https://github.com/apache/doris/pull/63514
## Summary Add 5 regression cases covering CDC operational scenarios that currently have zero test coverage. All cases target invariants that matter when running a CDC job in production (slot/offset lifecycle, fail-fast misconfiguration errors, FE restart durability): | Case | Source | Guards | |---|---|---| | `test_streaming_mysql_job_offset_earliest` | MySQL | `offset=earliest` skips snapshot and replays binlog from the oldest position; subsequent DML still lands. Table name carries a UUID suffix so prior CI runs of the same case cannot leak binlog events through the include_tables filter. | | `test_streaming_postgres_job_publication` (Tests 5/6/7 added) | PG | `PostgresResourceValidator` fail-fast paths: user-provided `slot_name` does not exist; user-provided `publication_name` does not exist; user-provided publication exists but is missing required tables. Each error must be actionable. | | `test_streaming_postgres_job_drop_during_snapshot` | PG | `DROP JOB` issued mid-snapshot must still clean up the auto-managed slot and publication. The existing `test_streaming_postgres_job_publication` Test 1 only covers `DROP JOB` after a steady state. | | `test_streaming_postgres_job_special_offset_restart_fe` | PG | `CREATE JOB` with a JSON LSN offset survives FE restart: `currentOffset` is preserved and subsequent binlog DML still lands. Mirrors the existing MySQL `_special_offset_restart_fe`. Uses a pre-created user slot to pin WAL retention back far enough for the captured LSN to remain valid. | | `test_streaming_postgres_job_slot_lsn_advance` | PG | `pg_replication_slots.confirmed_flush_lsn` advances steadily, freezes after PAUSE settles, and resumes advancing after RESUME. No prior case asserts confirmed_flush_lsn at all — operationally this is the single most important slot health signal. | ## Test plan - [ ] regression-test runs locally -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
