-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
byte vector is incorrectly decoded as utf-8 string in ft result class #2275
Comments
@AnneYang720 did you find a workaround? |
What about using "backslashreplace" mode instead of "ignore"? |
@kamyabzad I think in this case, we should get the original bytes as result, rather than try any kind of unicode decoding? Since user may need to convert this back to a numpy array or float array. I don't see a good solution or workaround under current search result parsing codebase though, maybe we need some ideas from the maintainers. |
Make it possible to configure at field level how search results are decoded. Fixes: redis#2772, redis#2275
Make it possible to configure at field level how search results are decoded. Fixes: redis#2772, redis#2275
Make it possible to configure at field level how search results are decoded. Fixes: redis#2772, redis#2275
Version:
Platform:
Python 3.9.2 on Debian GNU/Linux 11
Description: The bytes is converted to string in the vector search results and there is an error in this conversion. The bytes including
b'\x80'
is converted to a wrong string.Example Code
The original bytes
b'\x80\x00\x00\x00'
is converted to string'\x00\x00\x00'
.Reason
The text was updated successfully, but these errors were encountered: