Raz Monsonego

Hi @claridgicus, thanks for reaching out! Which RediSearch version are you using? Can you please share: * Your full index definition (`FT.INFO `). * The queries you are dispatching *...

Hi @claridgicus, Thanks for the info. Let me make sure I understand you correctly - what you refer to as "sorts" are fields of your index that you may use...

Hi @jorge-anova, Thanks for reaching out! It should; this is a known limitation in our sorting mechanism with terms containing diacritics. Several developments are currently underway in this area, and...

Hi @sarthakgaur, Notice that RediSearch doesn't formally support Fedora 38. Nonetheless, take a look at `.install/install.sh` and make sure you have the packages it installs (for the relevant OS).

Hi @ABHIJEET-MUNESHWAR, Thanks for your report. Did you also have problems when there were less keys in the database? Please try to minimize the reproduction scenario if you can, so...

I can't reproduce your db from the text file you provided so I'm using a similar database with different values - and experiencing no such problems. When you have 7999...

@ABHIJEET-MUNESHWAR I tried several scenarios, populating the db with: * Only the two keys you depicted. * 8000 other keys with the same fields and different values. * A lot...

Hi @ABHIJEET-MUNESHWAR, There's no straight-forward tool to upload the data from the .csv file to RediSearch for your data, so it requires some playing around. I'll give it a shot...

Hi @ABHIJEET-MUNESHWAR, Sorry for the late response. Yes, I can reproduce the bug now, thanks. Will update after some looking around. BTW notice that for `@field3:value*`, `@field6:prefix*` and `@field7:value*` all...

Hi @ABHIJEET-MUNESHWAR, Sorry for the wait. I have played around with the script, and I see some weird behaviors: - When we use a `characters` string of length `