Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Why can't ATTU display sparse vector in the UI? #39591

Closed
1 task done
lingvisa opened this issue Jan 24, 2025 · 12 comments
Closed
1 task done

[Bug]: Why can't ATTU display sparse vector in the UI? #39591

lingvisa opened this issue Jan 24, 2025 · 12 comments
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@lingvisa
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

After a collection is created, when I click 'Data', it always fails to load sparse data with an error message as attached. This does't occur in earlier version.

Please see attached.

Expected Behavior

Sparse vector can be displayed correctly along with other fields in ATTU

Steps To Reproduce

Any collection with a sparse vector should be able to reproduce it.

Milvus Log

No response

Anything else?

Image
@lingvisa lingvisa added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 24, 2025
@xiaofan-luan
Copy link
Collaborator

Maybe later version of attu will support it.

Check your attu version. @shanghaikid is there a specific version recommeneded?

Also please upgrate milvus to 2.5.4 since we fix some critical issue here

@shanghaikid
Copy link
Contributor

what is your attu version? the error shows that you are trying to get milvus generated spares vector field which is not allowed to retrieve from milvus.

@lingvisa
Copy link
Author

We upgraded Milvus 2.4.11 to 2.5.3, not a clean install of Milvus. So probably Attu not upgraded.

@shanghaikid
Copy link
Contributor

ok, please try the latest attu, it should be good.

@lingvisa
Copy link
Author

Yes. Attu is updated to 2.5.0 now. Now in the UI sparse vector isn't displayed at all, while the old version displays sparse vectors as one of the fields. Is this intended?

@shanghaikid
Copy link
Contributor

Yes. Attu is updated to 2.5.0 now. Now in the UI sparse vector isn't displayed at all, while the old version displays sparse vectors as one of the fields. Is this intended?

attu won't display vector generated by milvus.

The error shows it. @zhengbuqian can you confirm this?

@yanliang567
Copy link
Contributor

/assign @zhengbuqian
/unassign

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 28, 2025
@yanliang567 yanliang567 added this to the 2.5.5 milestone Jan 28, 2025
@lingvisa
Copy link
Author

I updated to ATTU 2.5.0. Now only dense vector is displayed, and sparse vector isn't displayed. Just want to confirm whether this is intended. In previous versions, both vectors are displayed.

@xiaofan-luan
Copy link
Collaborator

Yes. Attu is updated to 2.5.0 now. Now in the UI sparse vector isn't displayed at all, while the old version displays sparse vectors as one of the fields. Is this intended?

attu won't display vector generated by milvus.

The error shows it. @zhengbuqian can you confirm this?

maybe we should ignore sparse vector field if data in data out is enabled?

@zhengbuqian
Copy link
Collaborator

Yes. Attu is updated to 2.5.0 now. Now in the UI sparse vector isn't displayed at all, while the old version displays sparse vectors as one of the fields. Is this intended?

attu won't display vector generated by milvus.
The error shows it. @zhengbuqian can you confirm this?

maybe we should ignore sparse vector field if data in data out is enabled?

Yes sparse vector field generated by Milvus BM25 function(introduced in Milvus 2.5) should not be displayed. It is some internal representation and makes little sense to the user.

@lingvisa is your sparse vector field the output field of a BM25 Function(as described in https://milvus.io/docs/full-text-search.md#Create-a-collection-for-full-text-search)? if so then it is expected behavior it is not displayed. If the sparse vector is a normal one generated and inserted from the client, then it should be displayed.

@zhengbuqian
Copy link
Collaborator

/assign @lingvisa

@yanliang567 yanliang567 modified the milestones: 2.5.5, 2.5.6 Feb 28, 2025
@yanliang567 yanliang567 modified the milestones: 2.5.6, 2.5.7 Mar 11, 2025
@zhengbuqian
Copy link
Collaborator

closing this due to inactivity, feel free to reopen if necessary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

5 participants