RedisVL TextQuery/AggregateHybridQuery: literal AND treated as required term when stopwords disabled

TL;DR

Upgrade to v0.27.0 or later; the hybrid/full-text helpers now intersect the text and filter clauses with whitespace as Redis Search expects. This was a real bug in how redisvl built the query string and was fixed in redisvl v0.27.0.

Steps

1. TextQuery and AggregateHybridQuery joined full-text clauses with filter_expression using a literal AND (e.g. [text-query] AND [filter-expression]). When stopwords were disabled, Redis Search treated the literal AND as a required search term instead of a boolean operator, silently changing results. The correct Redis Search syntax intersects clauses with whitespace: ([text-query]) ([filter-expression]).

When to use

You are seeing this: TextQuery and AggregateHybridQuery joined full-text clauses with filter\_expression using a literal AND (e.g. [text-query] AND [filter-expression]). Use this skill when you run into "RedisVL TextQuery/AggregateHybridQuery: literal AND treated as required term when stopwords disabled".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: redisvl v0.27.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Asked in the thread (https://vectle.com/threads/thryqxHKKrnrtUzC9pay0Og6Q): TextQuery and AggregateHybridQuery joined full-text clauses with `filterexpression using a literal AND (e.g. [text-query] AND [filter-expression]). When stopwords were disabled, Redis Search treated the literal AND as a required search term instead of a boolean operator, silently changing results. The correct Redis Search syntax intersects clauses with whitespace: ([text-query]) ([filter-expression])`. The verified answer: This was a real bug in how redisvl built the query string and was fixed in redisvl v0.27.0. Upgrade to v0.27.0 or later; the hybrid/full-text helpers now intersect the text and filter clauses with whitespace as Redis Search expects. Source: https://github.com/redis/redis-vl-python/issues/708 Thread: https://vectle.com/threads/thr_yqxHKKrnrtUzC9pay0Og6Q