Re: [I] Seeding HNSW Search [lucene]

2025-01-20 Thread via GitHub
seanmacavaney commented on issue #13634: URL: https://github.com/apache/lucene/issues/13634#issuecomment-2602462598 Thanks @benwtrent! -- 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

Re: [I] Seeding HNSW Search [lucene]

2025-01-20 Thread via GitHub
benwtrent closed issue #13634: Seeding HNSW Search URL: https://github.com/apache/lucene/issues/13634 -- 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: is

Re: [I] Seeding HNSW Search [lucene]

2025-01-20 Thread via GitHub
benwtrent commented on issue #13634: URL: https://github.com/apache/lucene/issues/13634#issuecomment-2602459537 This has now been merged! Huzzah! -- 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 t

Re: [I] Seeding HNSW Search [lucene]

2024-08-06 Thread via GitHub
seanmacavaney commented on issue #13634: URL: https://github.com/apache/lucene/issues/13634#issuecomment-2271094294 Thanks! I just opened a draft PR (#13635). To answer your questions: > The API, this is always tricky to get correct I've struggled a bit with this. The PR has an

Re: [I] Seeding HNSW Search [lucene]

2024-08-06 Thread via GitHub
benwtrent commented on issue #13634: URL: https://github.com/apache/lucene/issues/13634#issuecomment-2271052423 @seanmacavaney I like this idea (I remember reading this paper a while back and getting excited about it). A couple of concerns I have are: - The API, this is alway