[
https://issues.apache.org/jira/browse/LUCENE-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597062#comment-16597062
]
Tomás Fernández Löbbe commented on LUCENE-8466:
-----------------------------------------------
bq. Maybe we should start thinking about releasing 7.5 because of this bug
+1
Do you know if this bug was always present with index sorting or if there was a
regression?
> FrozenBufferedUpdates#apply*Deletes is incorrect when index sorting is enabled
> ------------------------------------------------------------------------------
>
> Key: LUCENE-8466
> URL: https://issues.apache.org/jira/browse/LUCENE-8466
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Priority: Critical
> Fix For: 7.5, master (8.0)
>
> Attachments: LUCENE-8466.patch
>
>
> This was reported by Vish Ramachandran at
> https://markmail.org/message/w27h7n2isb5eogos. When deleting by term or
> query, we record the term/query that is deleted and the current max doc id.
> Deletes are later applied on flush by FrozenBufferedUpdates#apply*Deletes.
> Unfortunately, this doesn't work when index sorting is enabled since
> documents are renumbered between the time that the current max doc id is
> computed and the time that deletes are applied.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
