mikemccand commented on PR #16418: URL: https://github.com/apache/lucene/pull/16418#issuecomment-5117415807
+1 for the overall idea/approach -- it is insanely surprising / unexpected that updating a DV field has the cost / write amplification (whole column for that segment even if just one doc was updated) it does today. This would fix that, at least for `BINARY` and `NUMERIC` cases. It does presumably make lookup slower (it's trading off faster indexing for slower searching), since each lookup will go through N stacks (newest to oldest), and those docs that were never updated would have the most added cost I think? Have you tested lookup performance vs number of updates applied? In practice it's likely negligible -- the other costs of searching (HNSW crawl, decoding/intersecting postings, whatnot) usually dominate vs looking up DV valuews for sorting, say. -- 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]
