navneet1v commented on issue #14341: URL: https://github.com/apache/lucene/issues/14341#issuecomment-2727640413
> What you primarily want in the referenced GH issue is the ability to filter on more metadata during traversal vs doing a pre filter on the candidate documents themselves. As Adrien pointed out, this is better solved with more efficient filtering approaches (I wonder if the recent work on ACORN would help?) > > This issue is more towards the niche use cases where multiple graphs for a given segment would work. Multi threaded queries and disjoint cluster representation seem to be the immediate choices. So what I have been thinking here is if at a segment level we add a capability of having multiple graphs and make the process of generating those graphs generic will solve the problem I mentioned in github issue. See overall, how you split your docs into multiple clusters can be a choice for the user who is configuring the codec. If user wants to use k-Means algo to do clustering then it can use it, but if there are lets say other parameters in the document then that can be used for clustering/building different HNSW graphs. -- 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
