[Bug]: If a collection is dropped, its aliases cannot be displayed by list_aliases()

[yhmo]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: v2.5.4
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

If a collection is dropped, its aliases cannot be displayed by list_aliaes()

Expected Behavior

list_aliaes() should display its aliases even if a collection is dropped.

Steps To Reproduce

1. create a collection
2. assign an alias to the collection
3. drop the collection
4. call list_aliaes(), the alias is not displayed

Milvus Log

No response

Anything else?

No response

[dosubot]

Hey @yhmo 👋, I'm here to help you with any bugs, questions, or contributions you have regarding Milvus. Let's work together to resolve your issue.

In Milvus v2.5.4, the behavior you're observing is actually the intended behavior. When a collection is dropped, any aliases associated with that collection are also dropped. This is confirmed by the test case test_alias_reuse_alias_name_from_dropped_collection, which shows that after dropping a collection, the list_aliases() function returns an empty list, indicating that the alias has been removed along with the collection ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[yanliang567]

it is forbidden to drop a collection that has any aliases linked since milvus 2.5.5. @yhmo is it fixing this issue?

/assign @yhmo
/unassign

[xiaofan-luan]

@yanliang567
this should already be fixed on latest master, please verify on it

[yanliang567]

yes, verified on v2.5.5.