[Bug]: [GOSDK] The Loaded property in the description collection result is always false

[ThreadDao]

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

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

Current Behavior

1. loaded collection
2. describe collection and collection. Loaded is always false

• case:

  func TestLoadCollection(t *testing.T) {
  ctx := hp.CreateContext(t, time.Second*common.DefaultTimeout)
  mc := createDefaultMilvusClient(ctx, t)
  
  // create -> insert -> flush -> index -> load
  prepare, schema := hp.CollPrepare.CreateCollection(ctx, t, mc, hp.NewCreateCollectionParams(hp.Int64Vec), hp.TNewFieldsOption(), hp.TNewSchemaOption())
  prepare.InsertData(ctx, t, mc, hp.NewInsertParams(schema, common.DefaultNb), hp.TNewDataOption())
  //prepare.FlushData(ctx, t, mc, schema.CollectionName)
  prepare.CreateIndex(ctx, t, mc, hp.NewIndexParams(schema))
  
  // load two replicas
  loadTask, err := mc.LoadCollection(ctx, clientv2.NewLoadCollectionOption(schema.CollectionName))
  common.CheckErr(t, err, true)
  err = loadTask.Await(ctx)
  common.CheckErr(t, err, true)
  
  // describe collection
  coll, err := mc.DescribeCollection(ctx, clientv2.NewDescribeCollectionOption(schema.CollectionName))
  common.CheckErr(t, err, true)
  log.Debug("collection", zap.Bool("loaded", coll.Loaded))
  require.True(t, coll.Loaded)
  
  res, err := mc.Query(ctx, clientv2.NewQueryOption(schema.CollectionName).WithConsistencyLevel(entity.ClStrong).WithOutputFields([]string{common.QueryCountFieldName}))
  common.CheckErr(t, err, true)
  count, _ := res.GetColumn(common.QueryCountFieldName).GetAsInt64(0)
  require.EqualValues(t, common.DefaultNb, count)
  }

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

[yanliang567]

any updates

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.