[
https://issues.apache.org/jira/browse/LUCENE-9855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313963#comment-17313963
]
Michael Sokolov commented on LUCENE-9855:
-----------------------------------------
> If we'd like to have another ANN algorithm, say LSH, we would switch the
>metadata building and encoding logic in the codec writer/reader
>implementation, is my understanding correct?
Right, we'd have conditional logic in `Lucene90VectorReader' and
Lucene90VectorWriter` that would do different things depending on the
`SearchStrategy`. The reader would have to be able to read a header from the
metadata including the strategy, and then read the remainder of the metadata
and other data differently, depending on the strategy.
Or we could make a new format for LSH and for any other ANN strategy that has a
different index file format.
> Reconsider codec name VectorFormat
> ----------------------------------
>
> Key: LUCENE-9855
> URL: https://issues.apache.org/jira/browse/LUCENE-9855
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/codecs
> Affects Versions: main (9.0)
> Reporter: Tomoko Uchida
> Priority: Blocker
>
> There is some discussion about the codec name for ann search.
> https://lists.apache.org/thread.html/r3a6fa29810a1e85779de72562169e72d927d5a5dd2f9ea97705b8b2e%40%3Cdev.lucene.apache.org%3E
> Main points here are 1) use plural form for consistency, and 2) use more
> specific name for ann search (second point could be optional).
> A few alternatives were proposed:
> - VectorsFormat
> - VectorValuesFormat
> - NeighborsFormat
> - DenseVectorsFormat
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
