[
https://issues.apache.org/jira/browse/LUCENE-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984205#comment-13984205
]
Robert Muir commented on LUCENE-5618:
-------------------------------------
{quote}
What sort of index corruption does this check detect? As I see it, the Codec
gets a subset of the fields that it already wrote.
{quote}
That the field numbers it is using are valid!
Please, stop pushing back on this. I will make this a blocker issue for 4.9.
Maybe we should disable the dv update tests and enable this check in the
meantime? This is the most fair.
I dont like this pushing back against completely valid checks.
> DocValues updates send wrong fieldinfos to codec producers
> ----------------------------------------------------------
>
> Key: LUCENE-5618
> URL: https://issues.apache.org/jira/browse/LUCENE-5618
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Fix For: 4.9
>
>
> Spinoff from LUCENE-5616.
> See the example there, docvalues readers get a fieldinfos, but it doesn't
> contain the correct ones, so they have invalid field numbers at read time.
> This should really be fixed. Maybe a simple solution is to not write
> "batches" of fields in updates but just have only one field per gen?
> This removes many-many relationships and would make things easy to understand.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
