lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4087) Provide consistent IW behavior for illegal meta data changes
Date Fri, 08 Jun 2012 15:46:23 GMT


Simon Willnauer updated LUCENE-4087:

    Attachment: LUCENE-4087.patch

here is a new patch adding documentation to & a reference to all DV Fields.
I added a bunch of tests including verification test that changing norms types actually fails.
I extended the type promoter a little to actually promote INT_16 & INT_8 to Float32 if
needed as well as INT_32 to FLOAT_64.

I think its ready
> Provide consistent IW behavior for illegal meta data changes
> ------------------------------------------------------------
>                 Key: LUCENE-4087
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: core/index
>    Affects Versions: 4.0
>            Reporter: Simon Willnauer
>             Fix For: 4.0, 4.1, 5.0
>         Attachments: LUCENE-4087.patch, LUCENE-4087.patch
> Currently IW fails late and inconsistent if field metadata like an already defined DocValues
type or "un"-omitting norms.
> we can approach this similar to how we handle consistent field number and:
> * throw exception if indexOptions conflict (e.g. omitTF=true versus
> false) instead of silently dropping positions on merge
> * same with omitNorms
> * same with norms types and docvalues types
> * still keeping field numbers consistent
> this way we could eliminate all these traps and just give an
> exception instead.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message