mikemccand commented on PR #15979: URL: https://github.com/apache/lucene/pull/15979#issuecomment-4682315444
> I think what I'm asking for here is some kind of syntactic sugar/API on top of all this to hide from the user the idea that we are generating multiple fields over the same data? I guess Lucene could maintain a map from "HNSW field f + label a -> HNSW field f_a"? I agree the current scope isn't perfect, but it's super hard even just to do this first step (the low level sharing), which it looks like is quite clean here (but I'm not done reviewing!). I'd love to see such sugar, and somehow support for `BooleanQuery`-like joining of these separate fields at search time, but let's defer that to later phases? Progress not perfection? Does the dedup'ing optimize the `==` case maybe? (Just for flushing). So if I index 100 different fields, all with precisely the same `float[]`. I guess this may be tricky -- we may always make a copy today. We can optimize that later. -- 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]
