Exception Handling for MilvusClientV2 in milvus-java-sdk 2.6.6

[divyaruhil]

Currently, milvus-java-sdk version 2.6.6 returns generic DEADLINE_EXCEEDED error for all connection-related issues (invalid host, wrong port, or certificate errors).
This makes it difficult to identify the root cause .
DEADLINE_EXCEEDED: CallOptions deadline exceeded after 7.780172042s. Name resolution delay 2.199438000 seconds. [closed=[], open=[[wait_for_ready, buffered_nanos=7788263209, waiting_for_connection]]]

As per our discussion, there’s no direct way to unwrap specific exceptions for MilvusClientV2.

[divyaruhil]

We would like to contribute to this !

[divyaruhil]

A new boolean parameter enablePrecheck has been added to ConnectConfig.
When this option is set to true, the SDK automatically performs several pre-check validations before establishing a connection to Milvus.

These validations help catch common configuration or connection issues early, by running the following checks:

validateHostname() – Ensures the provided host name can be resolved (detects DNS or typo errors).

validatePort() – Verifies that the specified port is valid and reachable.

validateCert() – Validates SSL/TLS certificates if a secure connection is enabled.

If any of these validations fail, a clear and descriptive MilvusClientException is thrown immediately — helping users identify misconfigurations before attempting an actual connection.

[divyaruhil]

hi @yhmo , when will be the version released with this change, will it be there in v2.6.8 ?

[yhmo]

Link the pr: #1674

Yes, the fix will be released in the next minor version v2.6.8. I plan to release it tomorrow(November 21).

[yhmo]

v2.6.8 has been released to Maven: https://repo.maven.apache.org/maven2/io/milvus/milvus-sdk-java/2.6.8/
Close this issue