You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a reason why using the .containing(text) in a filter on a @Searchable TextField is escaping spaces in the search query when it goes through QueryUtils.escape()? I think something else is escaping that escaping slash before the space again later in the search process. When I run the query on a field directly in redis-cli , it works, with or without the escape slash. When I run it through om-spring, it's not working, unless I escape the spaces when I save the data in the document field.
For example, I could run either of these through the cli:
and I get the expected results. However, if I run SEARCH_TEXT.containing("some data") through an EntityStream, and output the stream.backingQuery() method results, I see the 2nd query above, but get no results at all when the query runs.
If I escape the searchText field contents when saving the document (so that it's contents end up looking like some\\\\ data\\\\ for\\\\ you, then the EntityStream method will give the expected results on the unescaped search parameter. But I don't think the data is supposed to be like that. (It works fine on eq() filters when the text doesn't include the escape characters and the filter doesn't try to add them there.)
The text was updated successfully, but these errors were encountered:
Is there a reason why using the
.containing(text)
in a filter on a@Searchable
TextField is escaping spaces in the search query when it goes throughQueryUtils.escape()
? I think something else is escaping that escaping slash before the space again later in the search process. When I run the query on a field directly in redis-cli , it works, with or without the escape slash. When I run it through om-spring, it's not working, unless I escape the spaces when I save the data in the document field.For example, I could run either of these through the cli:
and I get the expected results. However, if I run
SEARCH_TEXT.containing("some data")
through an EntityStream, and output thestream.backingQuery()
method results, I see the 2nd query above, but get no results at all when the query runs.If I escape the searchText field contents when saving the document (so that it's contents end up looking like
some\\\\ data\\\\ for\\\\ you
, then the EntityStream method will give the expected results on the unescaped search parameter. But I don't think the data is supposed to be like that. (It works fine oneq()
filters when the text doesn't include the escape characters and the filter doesn't try to add them there.)The text was updated successfully, but these errors were encountered: