[
https://issues.apache.org/jira/browse/LUCENE-9855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313937#comment-17313937
]
Tomoko Uchida commented on LUCENE-9855:
---------------------------------------
I was almost throwing away this in facing the difficulty of naming; but
[~julietibs] would be right, we should pursue to give proper name to our
"vector"s (yes, I think it is certainly nothing other than "vector", although I
understand the term is already overloaded many times). NumericVectorsFormat or
VectorValuesFormat, otherwise DenseVectorsFormat, either one looks fine to me
if "VectorsFormat" is too vague for us.
On the other hand, when we closely look at the current the codec Writer/Reader
implementation, it seems to be tightly coupled with HNSW graph building and
encoding and searching. From my viewpoint we should manage to decouple HNSW
specific code from the Codec to resolve inconsistency between its name and
implementation in the near future...
> 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: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
