goutamadwant opened a new pull request, #11967:
URL: https://github.com/apache/seatunnel/pull/11967
### Purpose of this pull request
Related to #10394.
This adds the Google Cloud Storage source slice only.
- Reuses the existing multiple-table file source for formats, schema
discovery, splitting, and continuous discovery
- Supports `gs://` bucket URIs with object paths configured separately
- Supports Application Default Credentials, an optional service-account JSON
key file, and additional `fs.gs.*` properties
- Registers the connector in plugin mapping, distribution packaging, and
default plugin configuration
- Adds English and Chinese documentation and dependency license metadata
GCS sink, BigQuery, and AlloyDB are outside the scope of this PR.
### Does this PR introduce _any_ user-facing change?
Yes. Users can configure `GcsFile` as a source for files stored in Google
Cloud Storage. Existing file connectors are unchanged.
### How was this patch tested?
Added focused tests for bucket validation, ADC and service-account
configuration, property precedence, factory options, and Hadoop `gs` filesystem
class resolution.
Verified on JDK 8 and JDK 11:
```shell
./mvnw -pl seatunnel-connectors-v2/connector-file/connector-file-gcs test
./mvnw -q -DskipTests verify
```
Both focused runs passed with 8 tests. A credentialed GCS environment was
not available, so this PR does not claim a live cloud read.
### Check list
* [x] Added the GCS connector license and NOTICE information for the new
shaded runtime JAR.
* [x] Added English and Chinese connector documentation.
* [x] No update to `incompatible-changes.md` is required because this only
adds a new connector.
* [x] Connector packaging was reviewed:
1. Updated `plugin-mapping.properties`
2. Updated `seatunnel-dist/pom.xml`
3. Existing connector and file label scopes cover the new module
4. Focused tests cover configuration and the filesystem integration
boundary; no credentialed cloud E2E was added
5. Updated `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]
