Today when I'm trying to connect to Attu, I'm using an IP address and port.
that's not a very good solution when it comes to a milvus cluster running on K8s, especially when using the milvus operator and not the helm charts.

I'm not able to connect to milvus when running a cluster using the IP address ( I tried the proxy service's IP adress).
anyways, I think that using the service address should be supported:
if I have a service address like:

milvus.default.svc.cluster.local:19530

there's no reason using it in my micro services (using milvus python sdk) will work, but not with attu.

Describe the bug:

Users can not delete selected data in Data Query

Steps to reproduce:

1. select some item in Data Query
   

2. click the "Delete button", and delete the selected data
   

3. attu shows that the deletion was successful

4. refresh the attu，requery the data，In fact, the deletion was not successful.
   

5. Re-delete the selected data, The prompt error is as follows：
   

Attu version:
v1.22.10

Attu version:

Attu version:
2.0.3

Describe the bug:

In Data Preview or Data Query, fields whose data type is bool are not displayed!

Steps to reproduce:

1. Create a collection with at least on field typed Bool
2. Insert data (manually or automatically)
3. Use Attu to preview or query data

Attu version:
tested on the following versions:

• 2.1.4
• 2.1.5-dev
• 2.2.0

Describe the feature:
reload collection with setting replica_number on attu

Describe a specific use case for the feature:
when the collection has some problems, may be solved by reload collection, it's convenient to do it by attu. But now attu not supoport to reload with setting replica_number.

Describe the bug:
打开Attu 的user菜单栏报错，点击添加用户按钮报错

Steps to reproduce:
1.打开软件

2.点击左侧user菜单栏，右上角报错
Error: Error: 12 UNIMPLEMENTED: unknown method ListCredUsers for service milvus.proto.milvus.MilvusService

3.创建新用户时报错
Error: Error: 12 UNIMPLEMENTED: unknown method CreateCredential for service milvus.proto.milvus.MilvusService

Milvus version:
v 2.0.2

Attu version:
v 2.1.0

Describe the bug:
When I upgrade attu from 2.1.2 to 2.1.4 with Milvus2.1.2, I can't use the "Data Preview" tab to get sample data.And I got the following error "Type allow all->0 inmemory->1"

The other information:

1. collection is loaded and can be searched with sdk the attu；
2. collection's index is hnsw and is created after all data is inserted.

Steps to reproduce:
1.
3.
4.

Attu version:
2.1.3

Attu version:

Describe the feature:

Describe a specific use case for the feature:
idx, err := entity.NewIndexIvfPQ(entity.IP, 4096, 32, 8)

The distributed version of milvus deployed by helm, attu is enabled by default. Refer to the official documentation https://milvus.io/cn/docs/v2.0.x/attu_install-helm.md to access cluster services by mapping ports to local. Through port mapping, 127.0.0.1 can access the milvus cluster, and from the cluster server, the milvus service can be accessed through 10.255.196.189. The attu service works by default, but a network error is displayed when adding a milvus connection.

Describe the bug:
The Entity Count is wrong after deleting a piece of data.

Steps to reproduce:

1. the "cpp_collection" collection has 2 entities;
   

2. set the filters : "VECTOR_ID > 0", and do the search, find all the data
   

3. pick one piece of data ,and delete it.
   

4. the result shows ok
   

5. return the home page of zttu, find the Entity Count of "cpp_collection" is still 2, the right number should be 1
   

6. Checking the console log shows the following：
   uri : http://#host#:#port#/api/v1/collections
   response :
   

Attu version:
2.0.5

Attu version:
2.0.5

Describe the bug:
can not start attu by npm package.

$ attu
Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
Trace/breakpoint trap

Steps to reproduce:

1. # rpm -ivh attu-2.1.1.x86_64.rpm
2. $ attu
   Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
   Trace/breakpoint trap

Attu version:
2.1.1

Describe the bug:
As shown, tapping the icon in the bottom left corner of the node view will cause the page to be obscured

Steps to reproduce:
1.
2.
3.

Attu version: 2.1.0

Attu version: 2.1.0

Milvus aliases are great for migrating indices without changing client code/config.
It would be nice if Attu could:

• display them
• use them in the dropdown in the vector search screen.

Describe the bug:
When loading one of the partitions, the status shows an error

Steps to reproduce:

1. create three partitions in one collection， and insert data into each partition separately
   

2. load one of the partitions with python sdk

collection = Collection("sp_partiton") # Get an existing collection.
collection.load(["1"])

3. return the home page of attu, and find that the status of "sp_partion" is wrong
   

4. check the console log of url "http://#host:port#/api/v1/collections" shows the following：
   

Attu version:
2.0.5

Attu version:
2.0.5

Describe the bug:

Steps to reproduce:
1.
2.
3.

Attu version:

Attu version:

Describe the bug:

The string index of Milvus 2.1.4 has not been built. My table is empty. Neither ATTU nor Python code can build the string index normally. I have been waiting. The database files are growing continuously, but we haven't put data yet. (Installed by the k8s helm, the helm has updated milvus to the latest version.). The index of vectors can be builted normally.

Steps to reproduce:
1.
2.
3.

Attu version:
attu:v2.1.4
milvus:v2.1.4

Describe the bug:
1、点击query结果单选框，会选中所有结果。
2、点击一条query结果的单选框，后执行删除，接口响应OK，但无法删除数据
3、全选query结果，执行删除，无法删除数据

Steps to reproduce:
1.从左侧collection菜单进入，选择一个collection，load到内存
2.在选择的collection详情界面，输入query条件，点击Query
3.点击query结果其中一条的选择框
4.点击左上方删除图标

Attu version:
2.0.1

Describe the bug:
In https://github.com/zilliztech/attu#attu-doc, insight is still used rather than attu
For example
helm install my-release milvus/milvus --set insight.enabled=true
However in https://github.com/milvus-io/milvus-helm/blob/master/charts/milvus/values.yaml, attu is used as the key.

Steps to reproduce:
1.
2.
3.

Attu version:

Attu version:

Describe the bug:

删除了一批向量后，attu上面显示的还是未删除的数量，并且插入后还在增长

Attu version:
v2.2.0

Describe the bug:
When dim is large will cause copy failed

Steps to reproduce:

1. create collection with large dim
2. query data
3. click copy, failed

Attu version:
v2.0.5

Attu version:

Describe the bug:
I use nginx to proxy attu web interface in an internal network environment to internet, I get this error when click "Connect".

Steps to reproduce:

1. My host IP is 192.168.171.232, with milvus port 19530, insight port 3000. My docker started with HOST_URL=https://attu.mydomain.com:13679 and MILVUS_URL=192.168.171.232:19530
2. I installed nginx proxy for this host, expose port 13679 and use host name attu.mydomain.com with ssl on, and proxy it to 192.168.171.232:3000. here is my nginx conf:

server {
   listen       13679 ssl;
   server_name  attu.mydomain.com;
   root         /usr/share/nginx/html;
   ssl_certificate "/ssl/server.crt";
   ssl_certificate_key "/ssl/server.key";
   ssl_session_cache shared:SSL:1m;
   ssl_session_timeout  10m;
   ssl_ciphers ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
   ssl_prefer_server_ciphers on;
   location / {
           proxy_pass http://192.168.171.232:3000/;
           proxy_redirect default;
           add_header 'Access-Control-Allow-Origin' '*'; 
   }
}

3. I can access the website https://attu.mydomain.com:13679 on internet and connect milvus returns 200, but after connected, when access /api/v1/collections/statistics, it returns 401 Unauthorized. The attu server logs is here:

POST 200 /api/v1/milvus/connect 106.541 ms @ Mon, 27 Dec 2021 09:54:01 GMT ::ffff:192.168.171.232 from undefined Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.110 Safari/537.36 

GET /api/v1/collections/statistics 401 UnauthorizedError: Please connect milvus first

GET 401 /api/v1/collections/statistics 3.464 ms @ Mon, 27 Dec 2021 09:54:01 GMT ::ffff:192.168.171.232 from undefined Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.110 Safari/537.36

The web browser POST to https://attu.mydomain.com:13679/api/v1/milvus/connect post data is:

{"address":"192.168.171.232:19530"}

and the server returns data is:

{"data":{"address":"192.168.171.232:19530"},"statusCode":200}

Fine way:
I can access it when in the local internet. change HOST_URL to http://192.168.171.232:3000, then everything is fine.

Attu version:
zilliz/attu:latest

Milvus version:
milvusdb/milvus:v2.0.0-rc8-20211104-d1f4106

Can't set strong consistency level. It makes a collection with session consistency level.

Describe the bug:
attu can't connect to milvus ,return BadRequestError: Connect milvus failed, check your milvus address. try to connect milvus with milvus_cli will be ok on the same host.

Steps to reproduce:
1.docker run -p 8000:3000 -e HOST_URL=http://{ your machine IP }:8000 -e MILVUS_URL={your machine IP}:19530 zilliz/attu:latest
2.click the button try to connect to miluvs some times can connect, some time return back Connect milvus failed, check your milvus address
3.in the same time try to connect miluvs with milvus_cli can connect success,and list collections ok

Attu version:
zilliz/attu:latest

Attu version:
zilliz/attu:latest

Describe the feature:
Milvus now supports specify Consistency Level while creating collection and performing search and query. Please add this feature to Attu.

Describe a specific use case for the feature:

Describe the bug:

collection data preview error

Steps to reproduce:
1.
2.
3.

Attu version:
v2.1.4

Attu version:

Describe the bug:

Steps to reproduce:
1.
2.
3.

Attu version:

Attu version:

Error: Error: 14 UNAVAILABLE: Name resolution failed for target dns:{0.0.0.0}:8053

run code:
sudo docker run -d -p 8054:3000 -e HOST_URL=http://{127.0.0.1}:8054 -e MILVUS_URL={127.0.0.1}:8053 zilliz/attu:latest

Describe the bug:
I was installing the Milvus with attu using helm. Previously, in the version Milvus-2.1.4, there was no issue faced, but in Milvus-2.2.0, there is no option for the username and password and thus I cannot connect to Milvus through a graphical interface with the Milvus.
I have tested this with both attu version of 2.1.0 and 2.2.0. But the behavior is same.

Steps to reproduce:
I have been following this documentation https://milvus.io/docs/attu_install-helm.md

Following is the error that appears, when tried to connect.

milvus supports boolean type, attu should support as well.

• add boolean type on collection creation dialog
• add boolean support on schema panel
• add boolean support on query and search results.

Describe the feature:
Add interface to view milvus server version

Describe a specific use case for the feature:
Only after the user checks the version of the milvus server can they know which version of the sdk to use.

Describe the bug:
My searches are failing due to the nprobe paramter being the incorrect datatype. No matter what number I enter it fails with this error.

Steps to reproduce:

1. Search on binary vector data (I used 1024 dim vector) with BIN_IVF_FLAT index
2. Use the metric type TANIMOTO
3. Set nprobe to any valid number, e.g. 1 or 200

Attu version:
2.1.5 - but this issue was occurring for me in other recent versions

Milvus version:
2.2.0

1：Filter中根据条件搜索，范围太大了就搜索不出来，能不能加个limit条件
2：不能创建FLAT索引，按钮灰的
3：预览数据是否可以做到排序

Describe the feature:

• Display compaction state
• Button to start compaction

Describe the bug:

The table should be behind the popup after click on icon "people" on the left

Steps to reproduce:

1. click into collection
2. click on partition
3. then click the "people" icon on the left menu

Attu version:

latest image
Attu version:
latest image

Describe the bug:
已经Loaded Collections，正常查询有数据。然后通过JavaSDK 添加数据 milvusClient.insert(insertParam)。再查询也能查出新添加的数据，但 attu页面显示的Entity Count 数量没有加一。还是原来的数量。但在attu页面上查询数据又能查到。

Steps to reproduce:
1.
2.
3.

Attu version:
attu:v2.1.0
milvus:v2.1.0
Attu version:

Describe the bug:

Steps to reproduce:
1.
2.
3.

Attu version:

2.1.1
Attu version:

Describe the feature:
I'd like to use both Milvus and Attu with minimal fuss. Helm chart is the solution.

Describe a specific use case for the feature:
Test cases and fast local experiments, as well as easier production usage.

Use docker compose file to start attu :

Describe the bug:
the attu does not support the metric type "IP" in the "FLAT" mode.
In fact, we can do this operation with the sdk.

Steps to reproduce:
1.

2. we can not chose the Metric Type option "IP" in the "FLAT" mode

3. In fact, we can do the "IP" search with the sdk.

Attu version:

v2.0.5

Attu version:

Describe the feature:
Supports displaying QPS and Latency of milvus cluster.

Describe a specific use case for the feature:

Milvus currently supports loading multiple memory copies when loading data.
https://milvus.io/docs/v2.1.x/replica.md#In-Memory-Replica

It would be better if attu could also support this function.

Describe the bug:
Attu cannot access milvus

Steps to reproduce:
1.
2.
3.

Attu version:


helm install my-release milvus/milvus --set attu.enabled=true

kubectl edit svc my-release-milvus-attu

Attu version:

Describe the bug:

I install attu with milvus helm chart, and i get an error like follows when connecting milvus service:

Steps to reproduce:

1. helm install attu-3 milvus/milvus --set attu.enabled=true
2. Configure DNS on my computer: xx.xx.xx.xx milvus-attu.local
3. Visit http://milvus-attu.local
4. connect Milvus server: http://attu-3-milvus:19530

Attu version:
image: zilliz/attu:latest

https://milvus.io/docs/v2.0.x/attu_install-package.md
Using the deb package provided by the milvus official website, I got an error when converting the rpm package

Use the following command

alien --to-rpm --scripts attu_2.0.1_amd64.deb

get an error

Package build failed. Here's the log of the command (cd attu-2.0.1; rpmbuild --buildroot='/root/milvus_attu/attu-2.0.1' -bb --target x86_64 'attu-2.0.1-2.spec'):
错误：行 5：空的标签：Summary:
构建目标平台：x86_64
为目标x86_64构建

Guessing from the error, it should be added with explanatory text after the Summary.
It would be better if you can provide the rpm package directly

Describe the bug:

When I search in attu, I got the following error message:

Steps to reproduce:
1.
2.
3.

Attu version:
V 2.2.0

Describe the bug:
I've created a new collection with 2 fields: primary key and embedding. I've created a HNSW_PQ index on it and then loaded it into memory. I then port-forward to my Attu instance and when I try to use the search function I get this error in the console log:

http://localhost:3000/#/search

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'search')
    at SearchParams.tsx:59:39
    at Object.Io [as useMemo] (react-dom.production.min.js:168:377)
    at t.useMemo (react.production.min.js:23:113)
    at t.default (SearchParams.tsx:56:24)
    at oo (react-dom.production.min.js:157:137)
    at Ho (react-dom.production.min.js:180:154)
    at Ws (react-dom.production.min.js:269:343)
    at wl (react-dom.production.min.js:250:347)
    at Al (react-dom.production.min.js:250:278)
    at Nl (react-dom.production.min.js:250:138)

Steps to reproduce:

1. Create collection
2. Load embeddings
3. Create HNSW_PQ index
4. Load the index
5. At Attu startpage where it then shows the loaded collections, click "Vector search". The screen glitches and then goes blank.

Attu version:
2.0.5

Describe the bug:
Users can not select single item in Data Query results

Steps to reproduce:

1. Query data in collection, find results as shown in the figure below：
   

2. Clik the button, select single item
   

3. All options are selected
   
   Users can not select single item.

Attu version:
v1.22.10

Attu version:

Describe the bug:

The index creation progress bar always displays 0% when Milvus is creating the initial index (i.e. not reindexing).

Attu polls this endpoint: /api/v1/schema/index/progress?collection_name=some_collection&field_name=some_field&index_name=some_index

but Milvus 2.1.1 returns this response:

{statusCode: 500, message: "no index is created", error: "Bad Request"}

since the index hasn't been created yet.

Attu should probably report that the index doesn't exist yet, or is being created.
Ideally Milvus would report progress on initial index creation.

Steps to reproduce:

1. Create a Milvus collection
2. Add some data
3. Create an index on the vector field.
4. While the index is being created, visit /#/collections/some_index?activeIndex=1

Attu version:

2.1.0

Describe the bug:
在没有编辑nprobe参数前点击“Search”按钮，查询结果正常，页面显示正常。
然后修改nprobe参数值，再点击“Search”按钮，有结果列表，但页面提示错误信息如下。
fail to search on all shard leaders, err=fail to Search, QueryNode ID=17, reason=Search 17 failed, reason [UnexpectedError] Assert "adapter->CheckSearch(conf, index_type, field_indexing->indexing_->index_mode())" at /go/src/github.com/milvus-io/milvus/internal/core/src/query/SearchOnSealed.cpp:54 => [SearchOnSealed]Search params check failed err %!w()

Steps to reproduce:
1.
2.
3.

Attu version:
attu:v2.1.0
Attu version: