File tree Expand file tree Collapse file tree 1 file changed +8
-1
lines changed
content/commands/ft.search Expand file tree Collapse file tree 1 file changed +8
-1
lines changed Original file line number Diff line number Diff line change @@ -275,7 +275,7 @@ since: 1.0.0
275
275
stack_path : docs/interact/search-and-query
276
276
summary : Searches the index with a textual query, returning either documents or just
277
277
ids
278
- syntax : " FT.SEARCH index query \n [NOCONTENT] \n [VERBATIM] [NOSTOPWORDS] \n [WITHSCORES]\
278
+ syntax : " FT.SEARCH index query \n [NOCONTENT] \n [VERBATIM] \n [NOSTOPWORDS] \n [WITHSCORES]\
279
279
\ \n [WITHPAYLOADS] \n [WITHSORTKEYS] \n [FILTER numeric_field min max [ FILTER\
280
280
\ numeric_field min max ...]] \n [GEOFILTER geo_field lon lat radius m | km | mi\
281
281
\ | ft [ GEOFILTER geo_field lon lat radius m | km | mi | ft ...]] \n [INKEYS count\
@@ -344,6 +344,13 @@ returns the document ids and not the content. This is useful if RediSearch is on
344
344
does not try to use stemming for query expansion but searches the query terms verbatim.
345
345
</details >
346
346
347
+ <details open >
348
+ <summary ><code >NOSTOPWORDS</code ></summary >
349
+
350
+ ignores any defined stop words in full text searches.
351
+ </details >
352
+
353
+
347
354
<details open >
348
355
<summary ><code >WITHSCORES</code ></summary >
349
356
You can’t perform that action at this time.
0 commit comments