You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Julie Tibshirani (Jira)" <ji...@apache.org> on 2021/11/10 18:00:00 UTC
[jira] [Resolved] (LUCENE-10228) PerFieldKnnVectorsFormat can write
to wrong format name
[ https://issues.apache.org/jira/browse/LUCENE-10228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julie Tibshirani resolved LUCENE-10228.
---------------------------------------
Fix Version/s: 9.1
9.0
Resolution: Fixed
> 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
> Fix For: 9.1, 9.0
>
> Time Spent: 50m
> 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: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org