Redisson Search - ranking & how to properly use it #6298
Unanswered
PedroMPagani
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently I'm working on a design transaction system it contains the following fields:
OWNER - String
Customer - String
Date - Long
Price - Double
Where - String
My goal is to have redis-search usage of this. in which the field Date and price should be "sorted", basically, so I can get from the highest long (meaning the newest) or for example by price, the other fields i'll use for a player mechanism search aswell.
This is the current code I have for it, but the searches/ordering are not working as sort of index, that's something I'm sort of "sure".
What am I doing wrong? the more elements there are, the cost becomes hugely exponential, I understand the pattern search is "*",
but shouldn't the cost be sort of "constant" in terms of sorting/searching?
Beta Was this translation helpful? Give feedback.
All reactions