Results 290 comments of groot

> Facing the same issue when I load the data into collection using collection.load() pymilvus-2.2.1 milvus-cli-0.3.2 > > I have tried upgrading and downgrading them but any other combination results...

fastjson is included

2.2.8增加了IndexType.SORT,用于设置int8/int16/int32/int64/float/double的索引

Follow this guideline? https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#creating-an-environment

An environment is added: ![Screenshot from 2024-03-29 14-30-56](https://github.com/milvus-io/milvus-sdk-csharp/assets/2282099/897647b1-643e-4df5-a63c-8042e459260f)

1. 不会有内存淘汰策略 2. getLoadState() 3. loadCollection方法是幂等的

ok, we will try replace it in the next minor version.

@king1302217 [This article](https://jfrog.com/blog/cve-2022-25845-analyzing-the-fastjson-auto-type-bypass-rce-vulnerability/) mentioned "To fully remediate CVE-2022-25845, we recommend upgrading Fastjson to the latest version, which is currently 1.2.83." The java sdk is using this version: https://github.com/milvus-io/milvus-sdk-java/blob/64e42bf8ee7dd6ce0b6a789c45c5afc031aa987b/pom.xml#L96 So, can...

Currently, the `com.alibaba.fastjson.JSONObject` is used as input of InsertParam/UpsertParam/InsertRowsParam and output of SearchResultsWrapper/QueryResultsWrapper. If we replace it with `gson.JsonObject`, will cause lots of impact on users' client code.

Note: The work of replacing FastJson with Gson is not ready. Today we released two new minor versions v2.3.7/v2.4.1 to fix some blocking issues. Replacing FastJson with Gson is postponed...