Vikasht34 commented on issue #15520: URL: https://github.com/apache/lucene/issues/15520#issuecomment-3688170184
This feels like a real gap in Lucene’s API surface. Primary-key (unique ID) lookup is one of the hottest paths in Lucene-based systems, yet today users are forced through TermQuery / TermInSetQuery, which are optimized for scoring/iteration rather than “find one doc and stop”. This also seems like a natural place to eventually exploit bloom-style negative checks when available.I’d be happy to help drive it forward . Would it make sense to assign this issue to me? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
