lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-5618) DocValues updates send wrong fieldinfos to codec producers
Date Tue, 29 Apr 2014 11:17:15 GMT


Robert Muir commented on LUCENE-5618:

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.

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:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message