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]: Different collection names returned across V1 and V2 of API #33148

Closed
1 task done
billreynolds007 opened this issue May 19, 2024 · 3 comments
Closed
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@billreynolds007
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 2.3.x
- Deployment mode: Cloud
- MQ type(rocksmq, pulsar or kafka): NA   
- SDK version: NA, using axios and REST
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Given these seeming same API semantics
https://${MILVUS_URI}/v1/vector/collections
http://${MILVUS_URI}/v2/vectordb/collections/list

The results are different
V1 { code: 200, data: [ 'quick_setup', 'medium_articles' ] }
V2 { code: 200, data: [ 'test_table_2', 'test_table_4', 'test_table_3' ] }

The cloud console shows the V1 names.

Expected Behavior

Same names no matter the version of the API

Steps To Reproduce

const axios = require("axios");
const endpoint = axios.create({
  baseURL: "FILL_IN",
  headers: {
    "Content-Type": "application/json",
    "Authorization": `Bearer FILL_IN`,
  },
});

async function listCollectionsV1()
{
 // https://${MILVUS_URI}/v1/vector/collections
 try {
   const reply  = await endpoint.get( "/v1/vector/collections");
   console.log('V1', reply .data);
  }
 catch(ex)
  {
  console.log('V1', ex.message);
  // 404
  }
}

async function listCollectionsV2()
{
 // http://${MILVUS_URI}/v2/vectordb/collections/list
 var payload = { "dbName": "default" };
 const reply  = await endpoint.post( "/v2/vectordb/collections/list", payload);
 console.log('V2', reply .data);
 // { code: 200, data: [ 'test_table_2', 'test_table_4', 'test_table_3' ] }
}

listCollectionsV1();
listCollectionsV2();

Milvus Log

No response

Anything else?

No response

@billreynolds007 billreynolds007 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 May 19, 2024
@yanliang567
Copy link
Contributor

@billreynolds007 what is the cloud console you mentioned above? is it Attu? how many collection did you created actually?
/assign @billreynolds007
/unassign

@yanliang567 yanliang567 added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 20, 2024
@billreynolds007
Copy link
Author

The 'console' is the web browser one found at, https://cloud.zilliz.com/orgs. The medium_articles collection was populated via an option button on a web page and the quick_setup collection via https://docs.zilliz.com/docs/quick-start.

@yanliang567
Copy link
Contributor

The 'console' is the web browser one found at, https://cloud.zilliz.com/orgs. The medium_articles collection was populated via an option button on a web page and the quick_setup collection via https://docs.zilliz.com/docs/quick-start.

as you are running on zilliz cloud, please file a ticket in support.zilliz.com for privacy issue. I'd close this issue for now.

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/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

2 participants