What are must, should, and must_not clauses in a Qdrant payload filter?

Question

Accepted Answer

`must` expresses conditions that a point must satisfy, so multiple conditions inside the must set behave like an AND. `must_not` excludes points satisfying its conditions, providing NOT semantics. `should` expresses alternatives: conditions can be satisfied as alternatives according to the filter semantics, rather than requiring every condition. A common use is allowing a point to match one of several categories or values. The important engineering point is to read the complete filter structure rather than mapping every should mechanically to SQL OR. Nested conditions, minimum_should semantics, and combinations with must or must_not can affect the exact result set. A common mistake is confusing must_not with a normal boolean field and assuming should always means 'optional preference.' In Qdrant filters, the surrounding structure and conditions determine whether a clause is required, optional, or used as an alternative. Check the version-specific filter documentation for advanced nested behavior. from qdrant_client import QdrantClient

client = QdrantClient(url="http://localhost:6333")

result = client.query_points(
    collection_name="products",
    query=[0.1, 0.2, 0.3, 0.4],
    query_filter={
        "must": [
            {"key": "in_stock", "match": {"value": True}}
        ],
        "should": [
            {"key": "category", "match": {"value": "laptop"}},
            {"key": "category", "match": {"value": "tablet"}}
        ],
        "must_not": [
            {"key": "region", "match": {"value": "blocked"}}
        ]
    },
    limit=10,
)
 must is used for required conditions should represents alternatives within the filter structure must_not excludes matching points Nested and advanced filter semantics should be verified against the deployed Qdrant version

What are must, should, and must_not clauses in a Qdrant payload filter?

Boolean filter semantics

Scenario Questions

Follow-up Questions