Milvus-adapter cognee version update to support new API endpoints

[prasanjit101]

The current adapter doesn't support new API endpoint i.e., AttributeError: module 'cognee' has no attribute 'remember'
Currently, it is using cognee==0.5.6
And is not updated to be used with the latest version of Cognee 1.1.0
And is thus breaking.

[Ibis-L]

Hi, I'd like to work on this issue. I'm new to open source but have experience with vector DBs (ChromaDB, RAG pipelines). Can I take this?

[Ibis-L]

I was able to reproduce the issue locally on window 11, Python3.13, cognee 1.2.1.
Here are the Bugs that i found:-
1> Multiuser access control conflict
Milvus is not registered as a supported handler in cognee 1.0's new access control system.

2> Async event loop conflict
get_milvus_client() uses loop.run_until_complete() inside an already running async context.

Right now working on these issue to solve it.

[sahilkanger]

I've opened #146 for the concrete half of this: get_milvus_client() crashes on local milvus-lite URIs because it drives cognee's async file-storage helper from a sync method inside the running loop — swapped for a loop-safe os.makedirs.

For the KeyError: 'milvus' under ENABLE_BACKEND_ACCESS_CONTROL=True, I'd like to add a DatasetDatabaseHandler, but wanted to check the intended isolation model first. Unlike Qdrant, the Milvus adapter doesn't currently scope its client to database_name (the MilvusClient is built without db_name), and prune() drops every collection on the connection — so copying the Qdrant handler (dataset → vector_database_name, delete → prune()) would make deleting one dataset wipe all of them.

Doing it safely needs a real per-dataset scope. Two options:

• Server Milvus: create/drop a per-dataset Milvus database (db_name) and scope the client to it.
• milvus-lite: a per-dataset .db file (like the LanceDB handler), since lite doesn't support multiple databases.

Which direction do you prefer (or both, branching on URI)? Happy to build it once we align.