fxbing opened a new issue, #621: URL: https://github.com/apache/fluss-rust/issues/621
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss-rust/issues) and found nothing similar. ### Please describe the bug 🐞 After server type validation was introduced, the Rust client creates the bootstrap `ServerNode` as `ServerType::CoordinatorServer` during metadata initialization. That makes bootstrap fail when the configured bootstrap endpoint is a tablet server: the server advertises `TabletServer`, while the client expects `CoordinatorServer`, so the connection is rejected with `InvalidServerType`. A bootstrap endpoint is only a seed used to fetch metadata. Its concrete server role is not known before the first successful metadata/API version exchange, and the Java client initializes bootstrap nodes with `ServerType.UNKNOWN`. ### Solution Introduce `ServerType::Unknown` for bootstrap seed nodes and skip server type validation only for that expected type. Keep strict coordinator/tablet validation for normal server connections after metadata is loaded. ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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]
