You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Simon Willnauer (JIRA)" <ji...@apache.org> on 2012/06/08 09:39:27 UTC
[jira] [Commented] (LUCENE-4087) Provide consistent IW behavior for
illegal meta data changes
[ https://issues.apache.org/jira/browse/LUCENE-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291600#comment-13291600 ]
Simon Willnauer commented on LUCENE-4087:
-----------------------------------------
After talking about this to other committers during the conference I think this is really a bit more controversial than it seemed. Except of the DocValues behavior this all is pre-existing behavior. The discussion is similar to changing norms through IR and removing that capability did bring up some hard discussions. Yet, I think we should only solve the DocValues issue in the least intrusive way and discuss the omitNorms & IndexOptions behavior in a different issue. If we make all this throwing exceptions we almost introduce a schema here which makes lucene 4.0 very different in terms of RT behavior compared to previous versions.
> 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
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org