mingshl commented on PR #14729: URL: https://github.com/apache/lucene/pull/14729#issuecomment-3007050715
This is an exciting feature!! I think it's great idea to create a `LateInteractionField` that can multi-vector store values in the documents, but I have a question in search, when I try to look at the Function score query, it seems that for search request, it first runs a knn query, then we fetch the top N documents for maxSim reranker. In this case, we need to use a single vector for knn query, and then use multi-vectors for reranking. If we want to use late interaction model for search, after we get the multi-vectors from the model and try to construct the function score query, first, we need a way to pool the multi-vector into single vector, and put into knn query second, we would put the multi-vector into the lateInteractionFloatRerankQuery I can see this way, we can save a lot of computing for too many MaxSim calculation, when the array of vector is big. I am thinking if that worth a new query type that can handle both pooling and rerank, basically the above two steps together. https://github.com/apache/lucene/blob/8dc05f47e0c0bc1c66d530fa6525b96e536a39d0/lucene/queries/src/test/org/apache/lucene/queries/function/TestFunctionScoreQuery.java#L447-L452 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
