[
https://issues.apache.org/jira/browse/LUCENE-10228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17441821#comment-17441821
]
ASF subversion and git services commented on LUCENE-10228:
----------------------------------------------------------
Commit 53586d4231e8de2156483be3a9bf7766e81912f9 in lucene's branch
refs/heads/main from Julie Tibshirani
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=53586d4 ]
LUCENE-10228: Ensure PerFieldKnnVectorsFormat uses right format name (#432)
Before when creating a KnnVectorsWriter for merging, we consulted the existing
"PER_FIELD_SUFFIX_KEY" attribute to determine the format's per-field suffix.
This isn't correct since we could be using a new codec (that produces different
formats/ suffixes).
This commit modifies TestPerFieldDocValuesFormat#testMergeUsesNewFormat to
trigger the problem. Without the fix we it throws an error like
"java.nio.file.FileAlreadyExistsException: File
"_3_Lucene90HnswVectorsFormat_0.vem" was already written to."
> PerFieldKnnVectorsFormat can write to wrong format name
> -------------------------------------------------------
>
> Key: LUCENE-10228
> URL: https://issues.apache.org/jira/browse/LUCENE-10228
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Julie Tibshirani
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently when creating a KnnVectorsWriter for merging, we consult the
> existing "PER_FIELD_SUFFIX_KEY" attribute to determine the format's per-field
> suffix. This isn't correct since we could be using a new codec (that produces
> different formats/ suffixes).
> The attached PR modifies TestPerFieldDocValuesFormat#testMergeUsesNewFormat
> to trigger the problem. Without the fix we get an error like
> "java.nio.file.FileAlreadyExistsException: File
> "_3_Lucene90HnswVectorsFormat_0.vem" was already written to."
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
