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:45:23 UTC
[jira] [Updated] (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:all-tabpanel ]
Simon Willnauer updated LUCENE-4087:
------------------------------------
Attachment: LUCENE-4087.patch
This patch implements a solution for docvalues that tries best effort if and only if the given value can be indexed without loosing any information. The DV type of the indexed field might be different to the "stored" one but we won't loose any information. This patch also handles this per DWPT and not global. The idea is that type promotion will fix the diverging types during merges but we guarantee persistence per segment.
for example if somebody indexed VAR_INTS but adds a FIXED_INT_* afterwards it should work just fine. While if somebody starts with FIXED_INT_8 and moves up to FIXED_INT_16 IW throws a IllegalArgumentException.
The patch is still missing javadocs here and there but given the controversial nature of this issue I wanna put it up for discusssion.
> 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
>
>
> 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