Redis Cloud: Search Command Deprecations and Query Parsing Changes in Redis 8 – Redis Knowledge Base

Redis 8 unifies Search and introduces stricter command parsing rules.
This KB lists deprecated commands and options, explains how parsing behavior has changed, and describes what Redis Cloud customers should update to maintain compatibility with Redis 8.0 and later.

At a glance

Availability: Redis Cloud 8.0 and later
Applies to: Databases using Search or Query features (RediSearch module → RQE engine)
Impact: Deprecated Search commands and options no longer work; stricter parsing may cause older queries to return errors instead of empty results.
Behavior: Automatic enforcement in Redis Cloud with no opt-out available

Problem	Fast check	Action
`FT.ADD` or `FT.DEL` failing	Command error in logs or API response	Replace with native writes (`HSET` / `JSON.SET`) and deletes (`DEL` / `UNLINK`).
`FT.SEARCH` using `FILTER` or `GEOFILTER`	“Invalid argument” error	Convert filters to query syntax (`@price:[10 20]`, `@loc:[-73.98 40.75 5 km]`).
Queries with `NOSTOPWORDS`	Option ignored or rejected	Define STOPWORDS behavior at index creation.
Older dialect specified (1,3,4)	Query fails or returns 0 results	Use `DIALECT 2`.
Empty result on invalid query	Unexpected errors now shown	Fix syntax; invalid inputs now return explicit errors.
`FT.CONFIG` returns “unknown command”	Attempting to change Search configuration	Redis Cloud manages Search configuration internally; use supported API parameters only.

Redis 8.0 consolidates Search commands.
The following items are deprecated and must be replaced:

Deprecated command or option	Replacement	Example	Notes
`FT.ADD`, `FT.SAFEADD`	Use `HSET` or `JSON.SET`	`HSET user:1 name "Alice"`	Indexes automatically track HASH/JSON writes through RQE.
`FT.DEL`	Use `DEL` or `UNLINK`	`DEL user:1`	Removes document from index automatically.
`FT.GET`, `FT.MGET`	Use native reads	`JSON.GET user:1`	Read directly from Redis key.
`FT.CONFIG`	Use `CONFIG GET/SET`	`CONFIG GET search_*`	Engine config managed internally in Cloud.
`FILTER` / `GEOFILTER`	Use query syntax	`@price:[10 20]`, `@loc:[-73.98 40.75 5 km]`	Included in query string (no longer options).
`NOSTOPWORDS`	Use `STOPWORDS 0` at index creation	`FT.CREATE idx STOPWORDS 0 ...`	Query-time toggle removed.
`DIALECT 1, 3, 4`	Use `DIALECT 2`	`FT.SEARCH idx ... DIALECT 2`	Older dialects deprecated.

Redis Cloud now enforces full argument validation for Search and Aggregate commands.

Key updates

LIMIT now requires valid combinations (offset=0 when limit=0).
FT.CURSOR READ and FT.ALIASADD reject malformed arguments.
Expressions in APPLY clauses must use parentheses around exponents (for example, (@price ^ 2)).
Invalid input now returns explicit errors instead of empty results.
Default scorer changed from TF-IDF → BM25, which may affect query ranking.

Inventory commands.
Search all codebases or scripts for FT.ADD, FT.DEL, FT.GET, FT.CONFIG, FILTER, GEOFILTER, and NOSTOPWORDS.
Replace writes and deletes.
Use HSET or JSON.SET for writes and DEL or UNLINK for deletes. Indexes update automatically through RQE.
Update queries.
Convert filters to inline query syntax and remove unsupported flags.
Validate dialect.
Explicitly set DIALECT 2 for compatible syntax.
Review ACLs.
Cloud ACL categories (@read, @write) now include JSON, time-series, and query engine commands.
Test and redeploy.
Run validation queries and confirm no command errors in logs.

Test	Command	Expected result
Numeric range query	`FT.SEARCH idx "@price:[10 20]" LIMIT 0 10`	Returns matching documents
Geo query	`FT.SEARCH idx "@loc:[-73.98 40.75 5 km]"`	Returns nearby documents
Deprecated syntax	`FT.SEARCH idx * FILTER price 10 20`	Fails with “Invalid argument”
LIMIT rule	`FT.SEARCH idx "*" LIMIT 10 0`	Fails (invalid offset/limit)
ACL test	Run as user with `+@read` only	`FT.SEARCH` allowed; `JSON.SET` denied

Run these tests

CLI: FT.SEARCH idx "@price:[10 20]" LIMIT 0 5
API (Python): r.execute_command("FT.SEARCH", "idx", "@price:[10 20]", "LIMIT", 0, 5)

Symptom	Likely cause	Resolution
“Invalid argument” error	Deprecated option or syntax	Update to supported query syntax.
Empty results on upgrade	Dialect mismatch	Add `DIALECT 2`.
Ranking changes	BM25 scoring difference	Verify expected ordering, retune relevance thresholds.
ACL permission error	Updated category mapping	Adjust ACLs to include `@read` or `@write` as needed.
App crashes on `FT.*` calls	Deprecated command removed	Replace with native JSON/HASH operations.

For additional help migrating queries or diagnosing parsing errors, contact Redis Support and include your database ID and full command example.

Related to