[Bug]: Pymilvus 2.6.4 breaks `AsyncMilvusClient` in `MilvusVectorStore`

[Magolor]

Bug Description

Pymilvus 2.6.4 breaks AsyncMilvusClient in MilvusVectorStore, while downgrading pymilvus from 2.6.4 to 2.6.3 fixes the error. Probably related to pymilvus #3096?

Version

llama-index 0.14.8, llama-index-vector-stores-milvus 0.9.4, pymilvus 2.6.4

Steps to Reproduce

Install pymilvus 2.6.4 and use llama index to create a MilvusVectorStore instance:

from llama_index.vector_stores.milvus import MilvusVectorStore
vdb = MilvusVectorStore(uri=..., collection_name=..., dim=...)

Results in:

RuntimeError: no running event loop

Meanwhile, downgrading pymilvus from 2.6.4 to 2.6.3 fixes the error.

Relevant Logs/Tracbacks

File "/usr/local/python3/lib/python3.11/site-packages/llama_index/vector_stores/milvus/base.py", line 325, in __init__
  self._async_milvusclient = AsyncMilvusClient(
File "/usr/local/python3/lib/python3.11/site-packages/pymilvus/milvus_client/async_milvus_client.py", line 42, in __init__
  self._using = create_connection(
File "/usr/local/python3/lib/python3.11/site-packages/pymilvus/milvus_client/_utils.py", line 41, in create_connection
  loop = asyncio.get_running_loop()
RuntimeError: no running event loop

[selvamanigovindaraj]

Hi @logan-markewich

I'd like to work on fixing issue #20313. The problem is that pymilvus 2.6.4's AsyncMilvusClient requires a running event loop during initialization.
Proposed solution: Implement lazy initialization for AsyncMilvusClient:

• Store connection params in init
• Create the client lazily via aclient property when first accessed (in async context)

Can I proceed with a PR?