issue4136

issue4130

Hello!
Could you tell me please what happened with 11.0 milvus? Its weird by it looks like deprecated, but 10.5 looks like actual. Which version should i take? I also ask because golang sdk 0.45 using float32 in Entity struct ->
it probably means less accurate search and i need float64 - but it is only in the sdk version 5.0.0 for milvus version 11.0.
Please help:)

Sorry if this is a frequent question

grpcClient has lots of function implementing Client interface. Currently they are organized into dm/dd file but the criteria is vague and hard to understand.
The APIs shall be organized into the object it manipulates format say client_grpc_collection.go contains all the functions related to Collection manipulation.

Below are the logs:

2020/03/23 20:21:10 [Recovery] 2020/03/23 - 20:21:10 panic recovered:
runtime error: integer divide by zero
D:/Go1.14.1/src/runtime/panic.go:191 (0x432b2a)
D:/GoPath/pkg/mod/github.com/milvus-io/[email protected]/milvus/ClientProxy.go:186 (0x849aea)

Is there 0.3.0 version ？

when the vectors' id of this collection is auto-generated id, the INSERT method should return IDs in response.

Search with index returns error with such message

Error in virtual milvus::knowhere::DatasetPtr milvus::knowhere::I

It's actually caused by params with wrong value type,say params = {"nprobe": "8"}, while correct params should be {"nprobe": 8}
note 8 should be number instead of string

API client.Flush, with async set to false, needs to wait until all the segments pre-created is flushed.
The checking condition is not correct since GetPersistentSegmentInfo will not returns unflushed segments info.

The correct import path should be "github.com/milvus-io/milvus-sdk-go/v2 instead of github.com/milvus-io/milvus-sdk-go/v2

The API draft has only column-based API while row based logic is more familiar to Gophers. Row based API should be supported for trial

milvus-sdk-go should have ut to verify client side behavior

• client package unit test
• entity package unit test
• coverage over 80%

The Index interface has only flatIndex and GenericIndex implementation for now.
All the supported index type and related metric/param constraint shall be implemented.

New API has been added into pymilvus (PR here)

Same feature should be added in golang sdk as well.

search接口批量查询结果处理有bug，请确认

issue4137

A rough draft version is accomplished but there is no example to demonstrate how to use this SDK. tests package should be the integrated test code with milvus. An example package is needed to demonstrate the usage cases.

milvus-io/milvus#2295

There is no API document for 2.0.

Some integration test cases and example has compile error due to API change

CalcDistance should support ids and vectors paramters. Now only id parameters are supported.

milvus-io/milvus#2203

The method to retrieve data from Scalar column missing

Like Insert, Flush, CreateIndex needs a async flag to indicating whether the API call should wait for index building process is complete

issue4132

我用的版本是上面标红的版本
当我使用example时，报错

According to go version semantic standard, the package module name shall be github.com/milvus-io/milvus-sdk-go/v2 instead of github.com/milvus-io/milvus-sdk-go. All package import shall be changed as well

milvus.proto defines milvus service is not up to date.

Get entities by entity ids

Check if server version is 0.9.x

issue4137

ListPartitions sdk return collection_name with partition_name.

The columns_xxx.go is auto generated for each FieldType. But one field per type is to clumsy. It should be organized like indexes.

There are several parameter constraint in pymilvus/pymilvus-orm, say create collection name must not exist in current mivus instance, etc.
The go sdk should have the same behavior.

Is there any reconnection policy if there same problem with client network?