[
https://issues.apache.org/jira/browse/LUCENE-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-6019.
----------------------------------------
Resolution: Fixed
> IndexWriter allows to add same field with different docvlaues type
> -------------------------------------------------------------------
>
> Key: LUCENE-6019
> URL: https://issues.apache.org/jira/browse/LUCENE-6019
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/index
> Affects Versions: 4.10.1
> Reporter: Simon Willnauer
> Assignee: Michael McCandless
> Priority: Critical
> Fix For: 5.0, Trunk, 4.10.2
>
> 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
> https://gist.github.com/s1monw/8707f924b76ba40ee5f3 /
> https://github.com/elasticsearch/elasticsearch/issues/8009
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
