Skip to content

branch-4.1: [test](streaming-job) refine cdc data-type and boundary regression cases for mysql/pg #63404#63668

Closed
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-63404-branch-4.1
Closed

branch-4.1: [test](streaming-job) refine cdc data-type and boundary regression cases for mysql/pg #63404#63668
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-63404-branch-4.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Cherry-picked from #63404

…ses for mysql/pg (#63404)

## Summary

- Update predicted `.out` values for cdc data-type / boundary regression
cases (mysql `enum_set`, `integer_boundary`, `json_types`; pg
`array_boundary`, `jsonb_types`, `time_types`, `uuid`) so expected
output matches the actual cdc-streamed values.
- Tune a few `.groovy` cases:
- `pg_array_boundary`: narrow the `multi_dim` column to 1D data; remove
the `array<text>` element with embedded `"` whose comparison is
non-deterministic.
- `pg_streaming_postgres_job`: drop the inline LIKE-wildcard "decoy
table" coverage (will return in a dedicated case once the underlying FE
handling is addressed separately).
- `mysql_enum_set` / `mysql_integer_boundary` / `mysql_json_types` /
`mysql_partition`: minor data adjustments to keep the suite stable.
- Add a pre-generated `.out` for
`test_streaming_mysql_job_charset_and_strings` whose groovy already
exists.
@github-actions github-actions Bot requested a review from yiguolei as a code owner May 26, 2026 07:44
@hello-stephen
Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

@JNSimba JNSimba closed this May 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants