-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
SEARCH command needs a limit option #51
Comments
As I just asked on #50 should stop words be specified at the time of indexing or from within the config file? In a future update results that are returned will be ranked based on some ranking algorithm (TD-IDF most likely) and sorted by most relevant results. a limit argument is interesting as well for search. I will consider that. |
Yeah, indexing with a
My point to rank option is more like Redis's ZSET, score, with user's defined function handler to customize. also, SEARCH with limit count to avoid the Redis's KEYS problem. |
Interesting idea with the StopTokenFile. I like that. As I mentioned in #50 we could specify a stop token list from the config file. Interesting idea allowing users to define their own ranking algorithm.. Maybe allow them to do that as an option? How would that work exactly though? Seems to me it'd be easier to just include a choice of ranking algorithm on Fist's end. |
Yeah, typically one dataset use one ranking algorithm, like tweets, INDEX tweets doc with some option like The option could be init at beginning, same as well, if two more dataset mix up in server, SEARCH is going to read skewed (some doc has |
like matt said #50 , need a stop words, or a limit output, or rank option(need INDEX support)
The text was updated successfully, but these errors were encountered: