benwtrent commented on PR #14792: URL: https://github.com/apache/lucene/pull/14792#issuecomment-2977917618
> Returning the vectors in search results Why would you need to do this? Generally, I would assume that any access to the vector would be "Give me what I gave you", and the best we can do with quantized vectors is the dequantized vector. I don't fully understand how serializing a read-only segment that is missing files (e.g. missing the "vec" file), but the format should do the right thing and see that the file isn't there and provide an approximate view of the floating point vectors. > Vector counting for metrics I don't understand what this means really. Just counting how many vectors there are? This should be doable via the `FloatVectorValues` interface. > but need to switch to quantizedVectorValues since searchers won't have float vectors anymore and we are okay in accepting the accuracy loss from float-to-byte quantization. Again, I think we should do the nice thing, de-quantize the vectors as the user asks for them. It should fully satisfy the `FloatVectorValues` API, de-quantizing the vectors and indicate that the vector returned is an approximation. Getting access to the raw quantized bytes is basically useless without all the other parameters that were used to quantized the vector. -- 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: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
