lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Reopened] (LUCENE-6019) IndexWriter allows to add same field with different docvlaues type
Date Wed, 17 Dec 2014 18:04:13 GMT


Michael McCandless reopened LUCENE-6019:
      Assignee: Michael McCandless

This commit caused LUCENE-6117, which Rob found & fixed (thanks!), but is too big to backport
to 4.10.x.

I think to fix it, I should revert the -Dtests.asserts part of this change (but keep the original
bug fix).

> IndexWriter allows to add same field with different docvlaues type 
> -------------------------------------------------------------------
>                 Key: LUCENE-6019
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 4.10.1
>            Reporter: Simon Willnauer
>            Assignee: Michael McCandless
>            Priority: Critical
>             Fix For: 4.10.2, 5.0, Trunk
>         Attachments: LUCENE-6019.patch, LUCENE-6019.patch
> IndexWriter checks if the DV types are consitent in multiple places but if due to some
problems in Elasticsearch users where able to add the same field with different DV types causing
merges to fail. Yet I was able to reduce this to a lucene testcase but I was puzzled since
it always failed. Yet, I had to run it without assertions and that cause the bug to happen.
I can add field foo with BINARY and SORTED_SET causing a merge to fail. Here is a gist
> While this is certainly a problem in Elasticsearch Lucene also allows to corrupt an index
due to user error which I think should be prevented. NOTE: this only fails if you run without
assertions which I think lucene should do in CI once in a while too.

This message was sent by Atlassian JIRA

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

View raw message