[
https://issues.apache.org/jira/browse/LUCENE-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291972#comment-13291972
]
Michael McCandless commented on LUCENE-4087:
--------------------------------------------
OK I guess that makes sense. Basically we sign up, now, to allow certain DV
type changes in the schema, just like how we allow omitNorms to change from
false to true, but not vice/versa.
> Provide consistent IW behavior for illegal meta data changes
> ------------------------------------------------------------
>
> Key: LUCENE-4087
> URL: https://issues.apache.org/jira/browse/LUCENE-4087
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
