[
https://issues.apache.org/jira/browse/LUCENE-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118410#comment-15118410
]
Erick Erickson commented on LUCENE-1761:
----------------------------------------
I've also seen this happen recently on 4.10.x. As in the original problem
statement the fields added were added because of an app bug.
We're seeing Lucene and Solr and ES being used in ever
larger-and-more-difficult-to-reindex situations. Thinking out loud here I
wonder if there's a way to accomplish this, perhaps as an option to checkindex
or maybe even a new index maintenance utility? What I'm thinking here is that
rather than make this part of the standard merge process, make it something
that has to be explicitly requested.
One advantage of that kind of utility would be users could back up the index,
run the utility then verify. That way they'd at least have a fallback if the
index became corrupted. That would also remove performance considerations from
the normal processing.
> low level Field metadata is never removed from index
> ----------------------------------------------------
>
> Key: LUCENE-1761
> URL: https://issues.apache.org/jira/browse/LUCENE-1761
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
