jpountz commented on PR #12064: URL: https://github.com/apache/lucene/pull/12064#issuecomment-1374770702
I haven't thought much about it but I'd prefer to avoid increasing the number of vector types that are supported, 2 already feels like a lot. For instance, terms and points only understand byte[] and push the problem of encoding data (numbers, strings) to sortable byte[]s higher up. It's a bit more complicated with vectors since it's not only about preserving order but maybe it's not that different? E.g. could hamming distance reuse the byte[] API by introducing a new distance function and half-float/bfloat16 reuse the float[] API? -- 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
