benwtrent commented on issue #13699: URL: https://github.com/apache/lucene/issues/13699#issuecomment-2374032761
I have been thinking more and more of how we can pass "custom" or "complex" parameters via the API. FWIW, this greediness is honestly focused on graph based indices only. If we ever did another type of index, its behavior would change. This is a similar conversation around folks adding `efSearch` as a parameter. Or possibly custom kNN collector behavior (your own early stopping logic...). A more opaque "hnsw knn search parameters" might be a better way, with a simple interface that is accepted in the queries. But adding an individual parameter for all the things you can do during query time with graph exploration would be complicated. -- 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
