Add an Azure Queue Storage sink connector
Implemented a production-oriented Azure Queue Storage sink with bounded asynchronous delivery, checkpoint flushing, error propagation, documentation, packaging, and Azurite-based integration coverage.
apache/seatunnel · #11939
New connector feature
SeaTunnel can now deliver bounded, at-least-once asynchronous sink workloads to Azure Queue Storage with multiple authentication and encoding modes.
Problem
SeaTunnel had no native Azure Queue Storage sink, leaving users without a project-supported path for authenticated, format-aware, backpressured queue delivery integrated with checkpoint lifecycle semantics.
Approach
Added connection-string, shared-key, and SAS authentication; JSON and text formats; plain and Base64 encoding; bounded request concurrency; checkpoint and close flushing; encoded-size validation; asynchronous failure propagation; connector registration; and E2E infrastructure.
Impact and scope
- Adds a complete Azure Queue Storage delivery path to the SeaTunnel connector ecosystem.
- Bounds in-flight work and propagates asynchronous failures so checkpoint success accurately reflects delivery state.
- Ships the operational surface around the connector, including packaging, licenses, bilingual documentation, registration, and Azurite E2E coverage.
Validation
- Added 19 focused tests covering authentication, options, serialization, encoded-size limits, concurrency, flushing, failures, and factory creation.
- Included an Azurite-backed E2E module and connector registration checks.
- Received maintainer approval; all authored commits and the upstream merge commit are GitHub-verified.