yzeng1618 opened a new pull request, #10180:
URL: https://github.com/apache/seatunnel/pull/10180
<!--
Thank you for contributing to SeaTunnel! Please make sure that your code
changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
## Contribution Checklist
- Make sure that the pull request corresponds to a [GITHUB
issue](https://github.com/apache/seatunnel/issues).
- Name the pull request in the form "[Feature] [component] Title of the
pull request", where *Feature* can be replaced by `Hotfix`, `Bug`, etc.
- Minor fixes should be named following this pattern: `[hotfix] [docs] Fix
typo in README.md doc`.
-->
### Purpose of this pull request
This pull request adds regex-based table matching support for the Kudu source
connector, including:
- A new optional option `use_regex` for Kudu source.
- Regex matching on `table_name` to read multiple tables with a single
configuration (including whole-database style matching).
It addresses the requirement that Kudu should support multi-table /
whole-database reading similar to the JDBC connector's `use_regex` behavior.
<!-- Describe the purpose of this pull request. For example: This pull
request adds checkstyle plugin.-->
### Does this PR introduce _any_ user-facing change?
Yes.
**Previous behavior**
- Kudu source only supported:
- Single table via `table_name`.
- Multiple tables via `table_list` with exact `table_name` entries.
- There was no official way to:
- Use regex to expand `table_name` into multiple tables.
- Implement whole-database style synchronization via a single pattern.
**New behavior**
- New option `use_regex` is added to Kudu source options:
- When `use_regex = true`, `table_name` is treated as a regex pattern and
all Kudu tables whose names match this pattern are read.
- When `use_regex = false` or not set, `table_name` is treated as an exact
table name (backward compatible with existing jobs).
<!--
Note that it means *any* user-facing change including all aspects such as
the documentation fix.
If yes, please clarify the previous behavior and the change this PR proposes
- provide the console output, description and/or an example to show the
behavior difference if possible.
If possible, please also clarify if this is a user-facing change compared to
the released SeaTunnel versions or within the unreleased branches such as dev.
If no, write 'No'.
If you are adding/modifying connector documents, please follow our new
specifications: https://github.com/apache/seatunnel/issues/4544.
-->
### How was this patch tested?
1. Unit tests
Added KuduSourceTableConfigTest to verify:
- parseKuduSourceConfigWithRegex correctly expands a regex table_name =
"kudu_source_table_\\d+" into multiple KuduSourceTableConfig instances.
2. E2E tests
Updated Kudu e2e
module(seatunnel-e2e/seatunnel-connector-v2-e2e/connector-kudu-e2e):
- kudu_to_assert_with_pattern_tables.conf + testKuduMultipleReadWithRegex:
Uses table_name = "kudu_source_table_\\d+" and use_regex = true to read
multiple tables via a single pattern.
- kudu_to_assert_with_all_tables.conf +testKuduWholeDatabaseRead:
Uses table_name = ".*" and use_regex = true to simulate whole-database
style synchronization.
- kudu_to_assert_with_table_list_pattern.conf + testKuduTableListWithRegex:
Uses table_list combining exact entries (kudu_source_table_1,
kudu_source_table_2) and a regex entry (kudu_extra_.* with use_regex = true),
and validates that all three logical tables are seen.
<!--
If tests were added, say they were added here. Please make sure to add some
test cases that check the changes thoroughly including negative and positive
cases if possible.
If it was tested in a way different from regular unit tests, please clarify
how you tested step by step, ideally copy and paste-able, so that other
reviewers can test and check, and descendants can verify in the future.
If tests were not added, please describe why they were not added and/or why
it was difficult to add.
If you are adding E2E test cases, maybe refer to
https://github.com/apache/seatunnel/blob/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-mysql-e2e/src/test/resources/mysqlcdc_to_mysql.conf,
here is a good example.
-->
### Check list
* [ ] If any new Jar binary package adding in your PR, please add License
Notice according
[New License
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/contribution/new-license.md)
* [*] If necessary, please update the documentation to describe the new
feature. https://github.com/apache/seatunnel/tree/dev/docs
* [*] If necessary, please update `incompatible-changes.md` to describe the
incompatibility caused by this PR.
* [ ] If you are contributing the connector code, please check that the
following files are updated:
1. Update
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
and add new connector information in it
2. Update the pom file of
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
3. Add ci label in
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
4. Add e2e testcase in
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
5. Update connector
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)
--
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]
