Known limitations

Updated May 23, 2026

Arbitrary filter parsing

The filter parameter on qdrant_find has limited support. The allow_arbitrary_filter configuration option exists but is not yet functional. Arbitrary JSON filter parsing is not implemented because Qdrant's protobuf Filter type does not implement serde's Deserialize trait, requiring manual construction from JSON structures.

Current behaviour: Providing a filter value in a qdrant_find request returns an error:

  • If allow_arbitrary_filter is false (default): "Arbitrary filters are not enabled"
  • If allow_arbitrary_filter is true: "Arbitrary JSON filter parsing is not yet implemented"

Workaround: Use the filterable_fields configuration to enable metadata filtering on specific fields. When entries are stored with metadata, the specified fields become searchable through Qdrant's native filtering capabilities.

Tracking: This limitation is tracked in GitHub issue #2.

[^1]: Either QDRANT_URL or QDRANT_LOCAL_PATH must be set, but not both.

[^2]: See "Collection name interpolation" for supported placeholders.

[^3]: Arbitrary filter support requires additional configuration and is not enabled by default. See "Known limitations" for details.