lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LUCENE-6019) IndexWriter allows to add same field with different docvlaues type
Date Thu, 23 Oct 2014 15:03:34 GMT


ASF subversion and git services commented on LUCENE-6019:

Commit 1633830 from [~mikemccand] in branch 'dev/trunk'
[ ]

LUCENE-6019: add more safety during DV flush

> 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
>            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