vigyasharma commented on PR #13525: URL: https://github.com/apache/lucene/pull/13525#issuecomment-2439879963
> it seems like single vector is a special form of multi-vector re: single v/s multi-vectors, I think it makes sense to not force users to chose multi-valued fields upfront. There's value in being able to go from single to multi-values when the need arises (and treating single-vectors like a storage optimization). However, I do think that we should not support changing the aggregation function once it has been set. Allowing different aggregate functions per segment will make merging and general debugging overly complicated. As such, I'm thinking of keeping the `Aggregation` as part of FieldInfo. There won't be a separate multi-vector field. When we create a vector without specifying the aggregation, the default gets set to `NONE` and only single values are allowed. Lucene validation will support going from `NONE` to a different value, at which point, the field is treated as multi-vector. However, changing the `Aggregation` once it is set to anything other than `NONE` will not be supported. How does this sound? -- 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
