Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
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]).
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
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
Source: https://github.com/redis/redis-vl-python/issues/708
Shows how to fix redisVL TextQuery/AggregateHybridQuery: literal AND treated as required term when stopwords disabled. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes NLTK LookupError for the stopwords resource by downloading it or pointing NLTK at the right data path.
Fixes NLTK's punkt_tab LookupError on NLTK 3.8.2 and later.