You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All you need to do is pass the consistency_level to the delete method. This bug is directly due to the use of kwargs.get in the function in order to populate a "new" keyword argument called consistency_level in addition to the existing one. It should happen no matter the other circumstances.
Environment details
- Hardware/Softward conditions: (OS: `6.10.0-linuxkit` Docker Desktop on Mac running Linux using the image `python:3.12-slim`, CPU: Apple M2 Pro, Memory: 8GB)
- Method of installation (Docker, or from source): A Docker image, as mentioned above. I'm using LangChain, so technically not calling the collection directly. `langchain-milvus==0.1.4`- Milvus version (v0.3.1, or v0.4.0): Milvus is running using the Docker image `milvusdb/milvus:v2.4.6`- Milvus configuration (Settings you made in `server_config.yaml`): Didn't change anything.
Anything else?
The bug is inherit in that call in the code, it basically will never work if consistency_level is provided. It looks like a direct result of this change: cb4cbc6
The solution could be to change the .get to .pop but it's worth making sure it's not going to be a problem with the line
Also optinal variables default value should always be None.
And empty str is always invalid variable
See also: milvus-io#2327
Signed-off-by: yangxuan <[email protected]>
Also optinal variables default value should always be None.
And empty str is always invalid variable
See also: milvus-io#2327
pr: milvus-io#2350
Signed-off-by: yangxuan <[email protected]>
Is there an existing issue for this?
Describe the bug
When I do
I get the following error:
Expected Behavior
To not fail
Steps/Code To Reproduce behavior
All you need to do is pass the
consistency_level
to thedelete
method. This bug is directly due to the use ofkwargs.get
in the function in order to populate a "new" keyword argument calledconsistency_level
in addition to the existing one. It should happen no matter the other circumstances.Environment details
Anything else?
The bug is inherit in that call in the code, it basically will never work if
consistency_level
is provided. It looks like a direct result of this change: cb4cbc6The solution could be to change the
.get
to.pop
but it's worth making sure it's not going to be a problem with the linewhich is also inside this function (I wasn't able to fully follow the logic of
MutationFuture
).The text was updated successfully, but these errors were encountered: