[Enhancement]: schema validation is fragile

[zhengbuqian]

Is there an existing issue for this?

• I have searched the existing issues

What would you like to be added?

currently we validate server schema by comparing with user provided schema

pymilvus/pymilvus/orm/collection.py

Line 134 in 76de0ab

if server_schema != schema:

.

with doc in doc out, we introduced tokenizer_params in params, which is a dict in user input, but a json string in server response. direct comparing will cause a failure.

now the tokenizer_params is simple so I used a temp resolution in #2298 to convert the json string back to a dict, but that will likely fail after we introduced more configs in tokenizer_params: keys in json may be reordered and the resulting dict will no longer equal.

Why is this needed?

No response

Anything else?

No response

[zhengbuqian]

/assign @zhengbuqian
/assign @XuanYang-cn

[zhengbuqian]

this should be fixed before the Milvus 2.5 release

[XuanYang-cn]

@zhengbuqian we could impl an __eq__ func in schema to cutomize what's need to compare and what could be ignored.

• Is Function going to change of the same collection? If so, then probably we should ignore it when validate schema.
• How does tokenizer_params looks like in Milvus? Please give an example of a classic tokenizer_params THX