You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2016/12/05 14:01:02 UTC

[jira] [Commented] (LUCENE-7581) IndexWriter#updateDocValues can break index sorting

    [ https://issues.apache.org/jira/browse/LUCENE-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722337#comment-15722337 ] 

Michael McCandless commented on LUCENE-7581:
--------------------------------------------

Thanks [~jim.ferenczi]; I think we need to fix the update DVs APIs to prevent changing any field involved in the index sort?

> IndexWriter#updateDocValues can break index sorting
> ---------------------------------------------------
>
>                 Key: LUCENE-7581
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7581
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Ferenczi Jim
>         Attachments: LUCENE-7581.patch
>
>
> IndexWriter#updateDocValues can break index sorting if it is called on a field that is used in the index sorting specification. 
> TestIndexSorting has a test for this case: #testConcurrentDVUpdates 
> but only L1 merge are checked. Any LN merge would fail the test because the inner sort of the segment is not re-compute during/after DV updates.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org