lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeffrey Morlan (JIRA)" <>
Subject [jira] [Commented] (LUCENE-1761) low level Field metadata is never removed from index
Date Fri, 18 Aug 2017 21:53:00 GMT


Jeffrey Morlan commented on LUCENE-1761:

We're trying to migrate from UninvertingReader to DocValues, and from Legacy*Field to *Point,
and this bug is causing searches to fail.

There are many fields that used to have values, but don't any more. Things that would work
fine if the fields were removed completely are failing because of the old field remnants:
DocValues.get* throws an IllegalStateException (unexpected docvalues type NONE for field 'foo')
PointRangeQuery throws an IllegalArgumentException (field="foo" was indexed with numDims=0
but this query has numDims=1)

> low level Field metadata is never removed from index
> ----------------------------------------------------
>                 Key: LUCENE-1761
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 2.2, 2.3, 2.3.1, 2.3.2, 2.4, 2.4.1
>            Reporter: Hoss Man
>            Priority: Minor
>              Labels: gsoc2014
>         Attachments: LUCENE-1761.patch
> with heterogeneous docs, or an index whose fields evolve over time, field names that
are no longer used (ie: all docs that ever referenced them have been deleted) still show up
when you use IndexReader.getFieldNames.
> It seems logical that segment merging should only preserve metadata about fields that
actually existing the new segment, but even after deleting all documents from an index and
optimizing the old field names are still present.

This message was sent by Atlassian JIRA

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

View raw message