yzeng1618 opened a new issue, #10697: URL: https://github.com/apache/seatunnel/issues/10697
### Search before asking - [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description ### What problem are you trying to solve? When SeaTunnel writes data to Doris through FE by using Stream Load, some jobs fail with `HTTP/1.1 307 Temporary Redirect` instead of returning the final Doris load result. From a user perspective, this makes Doris sink harder to use in real production deployments where FE redirects Stream Load requests to BE. The problem is more visible in environments with multiple FE nodes, private BE addresses, load balancers, Kubernetes networking, or cross-network routing. ### Why is this important? This issue can stop a full batch or streaming synchronization job even when the Doris cluster itself is healthy. It also makes troubleshooting harder because the raw `307 Temporary Redirect` may hide the actual Doris response. In one reproduced case, a manual request that follows redirects successfully returned the final Doris load result, while SeaTunnel only surfaced the raw redirect error. The final Doris response exposed the real load problem, which was much more useful for diagnosis. ### What would you like to achieve? I would like SeaTunnel Doris sink to provide a more reliable and user-friendly experience for Stream Load redirect scenarios. From a user perspective, the connector should: - work more predictably when Doris FE returns redirect responses during Stream Load - provide clearer diagnostics when redirect-related requests fail - expose enough compatibility or configuration support for deployments where FE-to-BE redirect is common - reduce the gap between SeaTunnel Doris sink behavior and what users already expect in the Doris ecosystem This request is not only about one temporary workaround for one job. It is about improving the reliability and usability of Doris sink in common real-world Doris deployments. ### Usage Scenario - Use SeaTunnel to synchronize data from JDBC sources such as PostgreSQL or MySQL into Doris - Run jobs in batch mode or streaming mode - Configure Doris sink with `fenodes` - Doris FE redirects Stream Load requests to BE - The deployment may include multiple FE nodes, internal BE addresses, SLB/Nginx/Kubernetes ingress, or separated network zones In these environments, users need SeaTunnel Doris sink to behave more robustly in redirect scenarios, or at least provide enough information to quickly identify the real root cause. A concrete reproduced example: - SeaTunnel version: 2.3.9 - Source: PostgreSQL JDBC - Sink: Doris - Symptom in SeaTunnel: `stream load error - HTTP/1.1 307 Temporary Redirect` - Manual verification with a redirect-following client can return the final Doris load result instead of stopping at the raw 307 response ### Related issues https://github.com/apache/seatunnel/issues/9871 https://github.com/apache/seatunnel/issues/9355 ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
