Conversation
… in favour of `None`
…d-alpha Remove client-side default `alpha` param for hybrid queries
Fix/tokenize simple output
# Conflicts: # weaviate/proto/v1/v4216/v1/base_search_pb2.py # weaviate/proto/v1/v4216/v1/base_search_pb2.pyi # weaviate/proto/v1/v5261/v1/base_search_pb2.py # weaviate/proto/v1/v5261/v1/base_search_pb2.pyi # weaviate/proto/v1/v6300/v1/base_search_pb2.py # weaviate/proto/v1/v6300/v1/base_search_pb2.pyi
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
| Secrets | View in Orca |
# Conflicts: # weaviate/proto/v1/v4216/v1/base_search_pb2.py # weaviate/proto/v1/v4216/v1/base_search_pb2.pyi # weaviate/proto/v1/v5261/v1/base_search_pb2.py # weaviate/proto/v1/v5261/v1/base_search_pb2.pyi # weaviate/proto/v1/v6300/v1/base_search_pb2.py # weaviate/proto/v1/v6300/v1/base_search_pb2.pyi
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
| Infrastructure as Code | View in Orca | ||
| SAST | View in Orca | ||
| Secrets | View in Orca | ||
| Vulnerabilities | View in Orca |
| return_metadata: The metadata to return for each object, defaults to `None`. | ||
| return_properties: The properties to return for each object. | ||
| return_references: The references to return for each object. | ||
| diversity_selection: Apply diversity selection (e.g. MMR) to the results. Requires Weaviate >= 1.37.0. |
There was a problem hiding this comment.
| diversity_selection: Apply diversity selection (e.g. MMR) to the results. Requires Weaviate >= 1.37.0. | |
| diversity_selection: Apply diversity selection (e.g. MMR) to the results. Since v1.37.0. |
nit(non-blocking): I think this is the more conventional way of phrasing that
There was a problem hiding this comment.
I'd rather be more explicit with requires so the user can't misunderstand
| ), | ||
| limit=3, | ||
| ).objects | ||
| assert [o.uuid for o in balance_0] != [o.uuid for o in balance_1] |
There was a problem hiding this comment.
If the goal of this is test is to see that "the client passes diversity_selection parameter to the server correctly", couldn't we just add 2 assertions here? One to check the effect of balance (i.e. order is different) and the other one to check the effect of limit (i.e. len(result) == mmr_limit).
3 distinct test cases just seems to be excessive for this. After all, 95% of the logic is server-side.
There was a problem hiding this comment.
Agreed, will try to combine them
There was a problem hiding this comment.
Similar to the comment above/below, do we need all 10 test cases for a 2-parameter config?
No description provided.