meiravgri

Hi @joeywhelan This indeed seems like a bug. Thanks for reporting.

Hi @ghczko we suspect it's related to the datatype. Can you please provide an example of a json record and the command that caused the crash? Thanks

Hi, thank you for reporting this issue. We're going to delve into it and will keep you informed. If additional information is needed, we'll reach out to you.

Hi @keithchew Thank you for bringing this to our attention! I have confirmed that there is indeed a bug. We are aware of it and are looking into potential solutions....

@keithchew fixing this bug is on our roadmap. If you have specific suggestions or ideas, please feel free to open a PR with your proposed fix. Thanks!

hi @zahidekilic Thanks for the report. I suspect that issue is caused by limited permissions on VM as reported here: https://github.com/RediSearch/RediSearch/issues/3581 To confirm, please run `cat /proc/cpuinfo` outside the docker,...

Unfortunately, it appears that changing permissions may not resolve the issue in this case However, I'd give it a try. The problem is likely related to the binary compilation for...

Hi @shohamazon. `NOINDEX` means that an inverted index won't be built for that specific field When you search for documents based on this field, you'll get zero results: for example:...

Yes, you got it right When using `SORTABLE ` the field won't be ignored entirely. The **values** of the field are stored in advance, ensuring accessing them during queries with...

Of course :) Seems like you caught a bug. ⭐ Thanks for bringing this to our attention. To better assist you, could you please provide more details about the specific...