DanielLeens commented on PR #10690: URL: https://github.com/apache/seatunnel/pull/10690#issuecomment-5119648130
Thanks again for adding the MaxCompute `tunnel_name` option. This PR is still useful because it lets users route Tunnel traffic through a named Tunnel Quota / exclusive resource group while keeping the default behavior unchanged when the option is not configured. I helped bring the original PR branch forward directly: - merged the latest `apache/dev` into `xxzuo:dev_odps_tunnel_name` - resolved the MaxCompute EN/ZH docs conflicts against the current option tables - kept the code path optional: `TableTunnel` only receives the quota name when `tunnel_name` is configured - ran scoped Spotless for `connector-maxcompute` - pushed the updated original branch to `add6eea2f9fcec69151eb9648b7dc43bdb3044c4` The PR is now mergeable from the conflict side. The remaining gates are the normal GitHub CI / review gates, and the fresh workflow jobs are queued on the updated head. Really appreciate the original contribution here. It is a practical connector option for users running MaxCompute in resource-isolated environments. -- 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]
