slfan1989 opened a new pull request, #634:
URL: https://github.com/apache/fluss-rust/pull/634
<!--
*Thank you very much for contributing to Fluss - we are happy that you want
to help us improve Fluss. To help the community review your contribution in the
best possible way, please go through the checklist below, which will get the
contribution into a shape in which it can be best reviewed.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [GitHub
issue](https://github.com/apache/fluss-rust/issues). Exceptions are made for
typos in JavaDoc or documentation files, which need no issue.
- Name the pull request in the format "[component] Title of the pull
request", where *[component]* should be replaced by the name of the component
being changed. Typically, this corresponds to the component label assigned to
the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are
unsure about which is the best component.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean
verify` passes.
- Each pull request should address only one issue, not mix up code from
multiple issues.
**(The sections below can be removed for hotfixes or typos)**
-->
### Purpose
Linked issue: close #585
Support comma-separated `bootstrap_servers` in the Rust client so users can
configure multiple bootstrap endpoints for high availability.
### Brief change log
- Parse `bootstrap_servers` as a comma-separated list of bootstrap endpoints.
- Trim whitespace around each endpoint and reject empty entries.
- Try bootstrap servers in order during metadata initialization until one
succeeds.
- Preserve existing single-bootstrap-server behavior.
### Tests
Added unit tests.
### API and Format
No public API or storage format changes.
### Documentation
No documentation changes.
--
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]
