Close rpc channel if MilvusClient fails to initialize

[yhmo]

No description provided.

[sre-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: yhmo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [yhmo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gemini-code-assist]

Summary of Changes

Hello @yhmo, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request improves the stability and resource management of the Milvus Java SDK by ensuring that gRPC channels are properly closed in scenarios where client initialization, connection establishment, or database validation fails. By wrapping critical initialization steps in try-catch blocks, the changes prevent potential resource leaks and contribute to a more resilient client implementation.

Highlights

• Resource Management: Introduced try-catch blocks in client initialization methods to ensure proper cleanup of gRPC channels.
• Error Handling: Implemented logic to close the gRPC channel if MilvusServiceClient or MilvusClientV2 fail to initialize or connect, preventing resource leakage.
• Client Robustness: Enhanced the robustness of client connections by handling exceptions during the initial connection and database validation phases.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces resource cleanup logic to close the RPC channel if the Milvus client fails to initialize, preventing potential resource leaks. The implementation in both MilvusServiceClient and MilvusClientV2 correctly wraps the initialization logic in a try-catch block. My review includes a suggestion to improve the handling of InterruptedException by restoring the thread's interrupted status, which is a best practice for robustness in concurrent environments.