goutamadwant opened a new pull request, #11939: URL: https://github.com/apache/seatunnel/pull/11939
### Purpose of this pull request Part of #10753. This pull request adds an Azure Queue Storage sink with a bounded asynchronous writer. The first version supports: - connection string, shared key, and SAS token authentication; - JSON and text message formats; - plain and Base64 message encoding; - configurable request concurrency; - flush on checkpoint preparation and close; - validation against Azure Queue Storage's encoded message-size limit; - errors from asynchronous sends propagated back to the SeaTunnel task. The connector follows SeaTunnel's at-least-once sink contract. Managed identity is intentionally outside this first slice so the connector does not add the larger Azure identity dependency graph before there is a concrete requirement. ### Does this PR introduce _any_ user-facing change? Yes. Users can configure `AzureQueueStorage` as a new sink connector. English and Chinese connector documentation describe authentication, delivery semantics, formats, limits, and configuration. ### How was this patch tested? Added 19 focused unit tests covering: - authentication and option validation; - JSON, text, and Base64 serialization; - encoded message-size enforcement; - bounded in-flight sends and checkpoint flushing; - asynchronous send failures; - factory creation. The connector registration checks pass. The Azurite E2E module and configuration are included and compile locally; the container-backed E2E execution remains a PR CI gate. ### Check list * [x] License and NOTICE material for the new Azure SDK dependencies is included. * [x] English and Chinese connector documentation and changelog entries are included. * [x] No incompatible change is introduced. * [x] `plugin-mapping.properties` is updated. * [x] `seatunnel-dist` is updated. * [x] CI label configuration is updated. * [x] An Azurite-based E2E test is added. * [x] `config/plugin_config` is updated. -- 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]
