nielifeng commented on issue #10063:
URL: https://github.com/apache/seatunnel/issues/10063#issuecomment-5140624803
I rechecked this against the current `dev` branch. The original report is
for 2.3.12, but the Doris sink has since gained two relevant changes:
- #10715 added an opt-in direct-to-BE stream-load path, specifically so
deployments can bypass an unstable FE redirect.
- #11330 fixed the default FE path when a slow `307` causes the
non-repeatable request body to be consumed before HttpClient follows the
redirect. Its regression test verifies FE -> BE redirect, HTTP 200, and full
body delivery.
For the `400 No Host` environment reported here, please retest with a
current `dev` build using the supported bypass:
```hocon
Doris {
fenodes = "fe1:8030,fe2:8030"
benodes = "be1:8040,be2:8040"
direct_to_be = true
# existing username/password/database/table options
}
```
Do not set `Host` in `doris.config`; use BE addresses reachable from the
SeaTunnel workers. With 2PC enabled, data writes use `benodes`, while
commit/abort still use `fenodes`.
I could not reproduce the exact Doris 2.1.11 `400 No Host` response locally,
so confirmation from the reporter environment is still valuable. However, no
new PR is needed at this point because the current `dev` implementation already
provides the redirect bypass and the later slow-redirect fix. Please share the
result with #10715 and #11330 included.
--
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]
