-
Notifications
You must be signed in to change notification settings - Fork 0
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
Flag to use index #61
Comments
@JohnGiorgi Do you think it's feasible/trivial to handle the following scenario: A request is made, having any of the existing required information ( In my mind, this just means picking off the uids in the Refs #81 (comment) |
I think I understand. Is this the exact same idea as #81 (comment), where there's some parameter passed in with a request, e.g. Alternatively, we could assume that if I think I could implement either pretty quickly. |
Yeah, the key point is that the set of uids provided get returned to the client. It could still use the index.
Sure that would be helpful, let me know if I can help. |
I'll take a stab at this - To test I guess we would need some mock/spy ? |
Right so I think you would basically add some argument to Then, you could copy and modify |
Perhaps this wasn't the issue I thought it was. What I was interested in was this scenario: You send the search say, 10 'document' uids, and you want to rank those documents and only those documents, in the result. I think many users have asked for this 'subset' search (here, here, here] and I think the answer is just use |
Ah right, I forgot FAISS doesn't let you filter. Yes, so you could perform the search on the whole index, then just filter the results so that they only contain the UIDs from documents in the query. You could add a new argument, or just overload |
Each query should allow for a flag (say
use_index
) that allows the user to not use/not use an index.The text was updated successfully, but these errors were encountered: