listDatabases is not supported on v2.6.0 of milvus?

[iGmainC]

Describe the bug:

code:

let client: MilvusClient = this.getClient();
console.log(client.connectStatus);
let { db_names } = await client.listDatabases();

log:

0
Error: listDatabases is not supported on this version of milvus.
    at Generator.next (<anonymous>)
 ⨯ unhandledRejection:  Error: listDatabases is not supported on this version of milvus.
    at Generator.next (<anonymous>)

Steps to reproduce:

Milvus-node-sdk version: v2.6.0

Milvus version: v2.6.0

[shanghaikid]

It does support. Did you config RBAC before? milvus or Zilliz Cloud?

yarn test test/grpc/Database.spec.ts                                                                                                                               [0]
yarn run v1.22.22
$ NODE_ENV=dev jest test/grpc/Database.spec.ts
  console.dir
    {
      db_names: [
        'database_b3gkgcmh',
        'database_fuaguk8h',
        'default',
        'newdb',
        'demo_knowledge_base_1',
        'demo_chat_history_2',
        'node_fetch',
        'fetch'
      ],
      created_timestamp: [
        '1755746778025150202',
        '1755746778039237085',
        '1754444210490862007',
        '1754444414606685311',
        '1754444438038825786',
        '1754444438817605953',
        '1754979452725716160',
        '1754979453030158762'
      ],
      db_ids: [
        '460098464386165371',
        '460098464386165373',
        '1',
        '459917023114083437',
        '459917023114083573',
        '459917023114083656',
        '459917023138533726',
        '459917023138533739'
      ],
      status: {
        extra_info: {},
        error_code: 'Success',
        reason: '',
        code: 0,
        retriable: false,
        detail: ''
      }
    }

[iGmainC]

It does support. Did you config RBAC before? milvus or Zilliz Cloud?

yarn test test/grpc/Database.spec.ts [0]
yarn run v1.22.22
$ NODE_ENV=dev jest test/grpc/Database.spec.ts
console.dir
{
db_names: [
'database_b3gkgcmh',
'database_fuaguk8h',
'default',
'newdb',
'demo_knowledge_base_1',
'demo_chat_history_2',
'node_fetch',
'fetch'
],
created_timestamp: [
'1755746778025150202',
'1755746778039237085',
'1754444210490862007',
'1754444414606685311',
'1754444438038825786',
'1754444438817605953',
'1754979452725716160',
'1754979453030158762'
],
db_ids: [
'460098464386165371',
'460098464386165373',
'1',
'459917023114083437',
'459917023114083573',
'459917023114083656',
'459917023138533726',
'459917023138533739'
],
status: {
extra_info: {},
error_code: 'Success',
reason: '',
code: 0,
retriable: false,
detail: ''
}
}

I'm not using RBAC, I'm just starting with the v2.6.0 official docker-compose file, setting the default root password using the COMMON_SECURITY_DEFAULTROOTPASSWORD environment variable.

[iGmainC]

docker-compose file:

services:
  etcd:
    container_name: milvus-etcd
    image: quay.io/coreos/etcd:v3.5.18
    environment:
      - ETCD_AUTO_COMPACTION_MODE=revision
      - ETCD_AUTO_COMPACTION_RETENTION=1000
      - ETCD_QUOTA_BACKEND_BYTES=4294967296
      - ETCD_SNAPSHOT_COUNT=50000
    volumes:
      - ./data/db/etcd:/etcd
    command: etcd -advertise-client-urls=http://etcd:2379 -listen-client-urls http://0.0.0.0:2379 --data-dir /etcd
    healthcheck:
      test: ["CMD", "etcdctl", "endpoint", "health"]
      interval: 30s
      timeout: 20s
      retries: 3

  minio:
    container_name: milvus-minio
    image: minio/minio:RELEASE.2024-12-18T13-15-44Z
    environment:
      MINIO_ACCESS_KEY: minioadmin
      MINIO_SECRET_KEY: minioadmin
    ports:
      - "9001:9001"
      - "9000:9000"
    volumes:
      - ./data/db/minio:/minio_data
    command: minio server /minio_data --console-address ":9001"
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
      interval: 30s
      timeout: 20s
      retries: 3

  standalone:
    container_name: milvus-standalone
    image: milvusdb/milvus:v2.6.0
    command: ["milvus", "run", "standalone"]
    security_opt:
    - seccomp:unconfined
    environment:
      ETCD_ENDPOINTS: etcd:2379
      MINIO_ADDRESS: minio:9000
      MQ_TYPE: woodpecker
      COMMON_SECURITY_DEFAULTROOTPASSWORD: '123456789'
    volumes:
      - ./data/db/milvus:/var/lib/milvus
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9091/healthz"]
      interval: 30s
      start_period: 90s
      timeout: 20s
      retries: 3
    ports:
      - "19530:19530"
      - "9091:9091"
    depends_on:
      - "etcd"
      - "minio"

[iGmainC]

code:

    let client: MilvusClient = this.getClient();
    await sleep(5000);
    console.log(client.connectStatus);
    let { db_names } = await client.listDatabases();

output:

2
Error: listDatabases is not supported on this version of milvus.
    at Generator.next (<anonymous>)
 ⨯ unhandledRejection:  Error: listDatabases is not supported on this version of milvus.
    at Generator.next (<anonymous>)

[iGmainC]

Why is the content of node_modules/@zilliz/milvus2-sdk-node/dist/sdk.json in @zilliz/milvus2-sdk-node v2.6.0:

{"version":"2.6.0","milvusVersion":"v2.6.0-rc1"}

[shanghaikid]

let client: MilvusClient = this.getClient();

Can you show me this.getClient ?

[shanghaikid]

const client = new MilvusClient({
...yourconfig
});

// usually you don't need this , but you can test to see if it works. 
await client.connectPromise;

[iGmainC]

const client = new MilvusClient({
...yourconfig
});

// usually you don't need this , but you can test to see if it works.
await client.connectPromise;

  getClient() {
    try {
      if (!global.milvusClient) {
        global.milvusClient = new MilvusClient({
          address: '127.0.0.1:19530',
          username: 'root',
          password: '123456789',
          database: 'xxx',
        });
      }
      return global.milvusClient;
    } catch (e) {
      console.error(e);
      throw e;
    }
  }

I think I've figured out the reason.

When using the standalone output mode for a NextJS project, you need to manually move some files from the .next directory to the standalone directory. After I did that, everything seems to be working fine.

[shanghaikid]

const client = new MilvusClient({
...yourconfig
});
// usually you don't need this , but you can test to see if it works.
await client.connectPromise;

getClient() {
try {
if (!global.milvusClient) {
global.milvusClient = new MilvusClient({
address: '127.0.0.1:19530',
username: 'root',
password: '123456789',
database: 'xxx',
});
}
return global.milvusClient;
} catch (e) {
console.error(e);
throw e;
}
}
I think I've figured out the reason.

When using the standalone output mode for a NextJS project, you need to manually move some files from the .next directory to the standalone directory. After I did that, everything seems to be working fine.

BTW, I will upgrade the error message, it's incorrect, thanks.

[iGmainC]

const client = new MilvusClient({
...yourconfig
});
// usually you don't need this , but you can test to see if it works.
await client.connectPromise;

getClient() {
try {
if (!global.milvusClient) {
global.milvusClient = new MilvusClient({
address: '127.0.0.1:19530',
username: 'root',
password: '123456789',
database: 'xxx',
});
}
return global.milvusClient;
} catch (e) {
console.error(e);
throw e;
}
}
I think I've figured out the reason.
When using the standalone output mode for a NextJS project, you need to manually move some files from the .next directory to the standalone directory. After I did that, everything seems to be working fine.

BTW, I will upgrade the error message, it's incorrect, thanks.

When using the v2.6.0 SDK in a NextJS environment, is it not necessary to add these lines to next.config.ts?

outputFileTracingIncludes: {
// When deploying to Vercel, the following configuration is required
'/api/**/*': ['node_modules/@zilliz/milvus2-sdk-node/dist/proto/**/*'],
},

It seems that node_modules/@zilliz/milvus2-sdk-node/dist/proto doesn't exist.

By the way, this doesn't necessarily have anything to do with standalone mode; I can't reproduce this issue right now.

[shanghaikid]

const client = new MilvusClient({
...yourconfig
});
// usually you don't need this , but you can test to see if it works.
await client.connectPromise;

getClient() {
try {
if (!global.milvusClient) {
global.milvusClient = new MilvusClient({
address: '127.0.0.1:19530',
username: 'root',
password: '123456789',
database: 'xxx',
});
}
return global.milvusClient;
} catch (e) {
console.error(e);
throw e;
}
}
I think I've figured out the reason.
When using the standalone output mode for a NextJS project, you need to manually move some files from the .next directory to the standalone directory. After I did that, everything seems to be working fine.

BTW, I will upgrade the error message, it's incorrect, thanks.

When using the v2.6.0 SDK in a NextJS environment, is it not necessary to add these lines to next.config.ts?

outputFileTracingIncludes: {
// When deploying to Vercel, the following configuration is required
'/api/**/*': ['node_modules/@zilliz/milvus2-sdk-node/dist/proto/**/*'],
},

It seems that node_modules/@zilliz/milvus2-sdk-node/dist/proto doesn't exist.

By the way, this doesn't necessarily have anything to do with standalone mode; I can't reproduce this issue right now.

Yes, no need to do so now.