gsmiller commented on issue #15520: URL: https://github.com/apache/lucene/issues/15520#issuecomment-3690161512
For starters, +1 to exploring this further and coming up with a more optimal way to include PK lookups in a query. I think there's something interesting here around use-cases that are looking up keys known to be in the index (or highly likely) vs. ones where the keys are fairly unlikely to be in the index. This could be application layer behavior (e.g., an application commonly needs to lookup keys that may not actually exist) or a result of a distributed index (e.g., multiple Lucene-based shards where only one will have the key). It also sounds like there might be some immediate wins to revisiting the `PKLookup` benchmark task to make sure we have the baseline we want before working on Lucene optimizations? -- 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]
